micro-editor / micro-editor/micro
Deprecate JSON configuration in favor of YAML
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
- YAML allows comments.
- YAML is backwards-compatible with JSON.
- YAML doesn't require as much boilerplate.
- YAML has better semantics for handling multiple documents within a single stream.
- YAML ain't markup language!
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
The issue names no files, tests, or entry points. Start by locating the editor's configuration loading and format-handling code, then review how JSON is currently supported and where YAML could be introduced. Done would require an agreed migration and deprecation plan, including compatibility expectations and updated tests or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, json, yaml
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100