fix(studio): persist studio state in project URLs#836
Merged
Conversation
miguel-heygen
approved these changes
May 14, 2026
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
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.
What
Persist key Studio state in project URLs.
Why
Refreshing Studio could lose the current composition, frame, panel state, and selection. That made it harder to reopen the same editing context.
How
Add URL state parsing and building for Studio project routes. Hydrate composition, frame, panel state, and selection from the URL (will add more based on user demand) with guards for stale state. Keep initial seek and selection restore stable when the preview adapter is not ready yet.
Test plan
How was this tested?