[DO NOT MERGE] Prototype showing component errors/warnings within the Components tree#17053
Closed
bvaughn wants to merge 1 commit into
Closed
[DO NOT MERGE] Prototype showing component errors/warnings within the Components tree#17053bvaughn wants to merge 1 commit into
bvaughn wants to merge 1 commit into
Conversation
|
This could be nice for troubleshooting those "unique key" errors. |
Contributor
Author
|
Interesting idea but not something I'm actively working on. |
This was referenced Dec 13, 2020
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
5 participants
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.
Relates to #9189
Last night I played around a bit with the idea of surfacing dev warnings/errors in the Components tree UI:
I'm not sure this is useful or compelling enough to warrant completing, and there are a few significant "TODOs", but I'm pushing in case myself or someone else decides to play with it some more in the future. (I'm not going to follow up with it for the time being.)