Isolated schema state for multiple editors
- Dominant language
- TypeScript
- Stars
- 84
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
When multiple editors are present on a single page, they all share a global schema state. when using setSchema on the worker, the schema object will be updated for all configurations. It would be great to be able to configure the editor to allow for each editor to maintain its own state individually.
Would a feature like this be present in the future roadmap?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the worker's setSchema path and how multiple editor configurations currently access the global schema state. Define how each editor should retain an independent schema, then verify that changing one editor's schema no longer changes the others.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100