-
-
Notifications
You must be signed in to change notification settings - Fork 19
Add stubs/no-op support for unsupported targets #426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add stubs/no-op support for unsupported targets #426
Conversation
Co-authored-by: giancarlo.buenaflor <giancarlo.buenaflor@sentry.io>
…for-sentry-kmp-235a
…s-browser-target-for-sentry-kmp-235a
js
and wasmJs
target
js
and wasmJs
target} | ||
|
||
private fun KotlinMultiplatformExtension.addNoOpTargets() { | ||
js(IR) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, should we use BOTH here? https://kotlinlang.org/docs/js-ir-compiler.html#authoring-libraries-for-the-ir-compiler-with-backwards-compatibility
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah I see, it's too old already
Note: this should not be merged before we fix craft to process the new targets
📜 Description
Users have bad devex if they use targets that we don't support.
Currently the SDK won't compile and the user would have to shift their sourceSet architecture which is unrealistic.
💡 Motivation and Context
Adds no-op support for
js
,wasm-js
,linux
,mingw
so users can freely use Sentry in the official supported targets and no-op targets.Closes #328
Closes #327
Closes #329