Developers lack reliable editor feedback for modern JSON and YAML schemas
Developers authoring schemas and schema-driven API or configuration editors report incomplete support for newer JSON Schema features, including draft 2020-12 and meta-schema features, as well as missing YAML validation and autocomplete. Some switch to CLI tools; others report significant work to wire schema support into embedded editors. The result is fragmented feedback while authoring or validating complex schemas and configuration.
For developers authoring API and configuration schemas. Mentioned from Jun 2019 to Jan 2026 on GitHub and Hacker News.
13 different people described this problem in 9 separate discussions.
- Indie fit
- 6.0/10
- Pain
- 6.0/10
- Frequency
- 9.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
Feature request: support JSONSchema with YAML I encountered this problem while developing an API Governance editor at Bloomberg -- took significant work to use monaco-yaml. Now I am encountering again at my new startup -- adding significant work.
The support that 2020-12 lays down for defining schema dialects is wildly useful for schema authors, but hand-crafting those definitions in VS Code means constantly moving from the editor to a CLI tool to validate the schema
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 11 more quotes from people who have this problem
- Current workarounds, existing solutions and risks