merge human-pane, source-pane and mardown-pane
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 146
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
these panes are related to text/xxx content.
The merged pane could automatically display the content depending on content-type.
The edit button will display the raw text and validate will check and display the content based on content-type
There may be a need to keep text/html apart to keep the pod web server function.
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
Start by locating the human-pane, source-pane, and markdown-pane implementations and trace how they handle text/xxx content types. Clarify the merged pane's display, raw-text editing, validation behavior, and whether text/html must remain separate; done means these decisions are implemented consistently.
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