More information in "outside reactive tracking context" warning #3831
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
As of now, the "outside reactive tracking context" warning often only points to internals of `reactive_graph`, making it hard to figure out where in the user code this was caused. This commit adds a backtrace that is printed after the warning. It has the caveat that it is a WASM backtrace, and hence contains less information than a Rust backtrace. However, [it is currently impossible to get a nice Rust backtrace out of WASM](https://users.rust-lang.org/t/what-is-the-current-state-of-backtraces-in-wasm/128002/2?u=isibboi), hence this seems to be the best option.
ISibboI
changed the title
|
Does this require the |
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.
As of now, the "outside reactive tracking context" warning often only points to internals of
reactive_graph, making it hard to figure out where in the user code this was caused. This commit adds a backtrace that is printed after the warning. It has the caveat that it is a WASM backtrace, and hence contains less information than a Rust backtrace. However, it is currently impossible to get a nice Rust backtrace out of WASM, hence this seems to be the best option.