Repository navigation
fix: apply the wasmUrl default only while the app has not configured wasm - #17
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wrapper side of SCJS-9224.
scichart-react's import-time
wasmUrl: "/scichart.wasm"default overwrote the app's ownSciChartSurface.configure(...)whenever the chart code was lazy-loaded (SciChart.JS.Examples worked around it in 3a6696f). The default is now applied throughapplySciChartConfigonly whileSciChartSurface.isWasmConfiguredis false, so the app's configuration wins in either order.>=6.0.8, all pins bumped.initChartare always markedisLifecycleManagedExternally; the guard for older cores is gone.demos/features/wasm-url-orderreproduces the original bug against scichart-react 2.0.0 from npm.