Split into two panes, source editor and text editor
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 3
- Avg merge
- 11h 46m
- Merged PRs (30d)
- 3
Description
The problem here is that when we are talking about a data file like, say, a meeting definition file, then this view is one only developers should get as an option as “Source view” of the data. When it is a plain text file, then a normal user should get it as the the default view of a plain text note file, so not “Source” or maybe “Text” or “View/edit” or something should be the pane name. So really it should be two panes, with different priorities and different targets and different icons and different labels.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. Start by locating the source-pane view and its current pane, label, icon, and file-type selection logic; then clarify the intended split and validate the result with the repository's available UI checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100