Improve read only performance when just displaying rich workspace
Open
Nobody has claimed this yet.
0. Needs triage
enhancement
feature: folder description
performance 🚀
- Dominant language
- JavaScript
- Stars
- 659
- Forks
- 133
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 110
Description
In most cases the rich workspace area is probably not edited, so we should think about having a more sane process for opening up a read only editor and just kicking of the heavy sync parts and session setup when starting to edit.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or an entry point. Trace how the rich workspace is opened and how read-only display currently starts editing, synchronization, and session setup; done means read-only display avoids those heavy paths until editing begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100