spring-projects / spring-projects/spring-tools
Explore json schema discoverability
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 983
- Forks
- 240
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 7
Description
Should we make discovery of relevant json schemas easier, such that they are easy to know they are available and when you grab one you get content assist in whatever json editor you are using. An example one would be the config server json schema (which might be available from pivnet already). Taking it further should we be including any json schemas directly for easy editing of some files? (Similar story for yml?)
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
No files, tests, or implementation entry points are named. First clarify whether the goal is to expose existing Config Server schemas, bundle schemas for selected files, support YAML as well as JSON, or all three; done requires an agreed scope and discovery experience for editor content assist.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json, yaml
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100