Visual JSON tree node editor in web UI
Open
Nobody has claimed this yet.
new feature
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
We currently use ACE editor for editing any files in the web UI, but a user may prefer using visual tree node editor for JSON or YAML. We may still want to fall back to ACE when:
- A user prefers ACE or
- The file is too large.
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 reviewing the web UI's current ACE editor integration and how it identifies JSON or YAML files. Define the visual tree editor's scope, the user preference and file-size conditions for falling back to ACE, and verify that both editing paths work for supported files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, yaml
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100