?inspector={element} and Entity.inspect() helpers to reduce inspector friction #3894
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
ngokevin
force-pushed
the
inspect
branch
3 times, most recently
from
b43bbb8 to
58e7b79
Compare
|
Should have waited for review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description:
When working with Inspector, there's friction in refreshing the scene + opening the Inspector + searching the entity / selecting the entity + repeat.
Changes proposed:
?inspector={elementId}URL parameter that automatically opens the Inspector and focuses on the passed-in entity (if any). Then if you are working in an Inspector workflow (e.g., tweaking an entity), just keep the URL parameter there and refresh.Entity.inspect()method to easily open/focus any entity in Inspector from DevTools console.If merged, matching Inspector changes will follow.