New JSON generator schema
@avivkeller ci sta già lavorando.
Dal 15/9/2026.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Enter your suggestions in details:
Background
This issue is regarding the new format for the JSON generator.
It only pertains to the format of the JSON files, the implementation details will be discussed once a censensus is reached here.
Why a new format?
There are a handful of issues with the current format, with some of the main ones being:
- Maintainability
- Without a pre-defined schema, it can be harder to tell where a property should be expected to go within the output
- There isn't a great way to communicate changes to this schema when they happen
- Consumability
- Users don't know what to expect without going through the generator's code or looking through all of the outputted JSON files
- The current format represents some fields in unfortunate ways (i.e. Markdown being parsed in HTML for descriptions)
Relevant: DefinitelyTyped/DefinitelyTyped#70298, nodejs/api-docs-tooling#57
The new format
The newly proposed schema for json generator is available here.
An example of it being used for Buffer is available here.
The new proposed schema for the json-all generator is available here.
An example of it being used is available here.
Key Points
JSON Schema
The new formats have JSON schemas defined. This gives us three main advantages over the current format:
- Consumers know what to expect
- We can version the output files in a standardized way (via the
$idproperty) - The schemas can be used to generate the types used within the JSON generator. This will help with maintaining the generator in the long run since we don't have to worry about them getting out of sync.
JSDoc Property Names
JSDoc keys (i.e. @name, @type) are used in the format.
This is mainly to make the files easier to consume.
TODOs
Here's what's left to be done with the new format:
- How do we want to represent sections that are just text (aka not defining any API)? Should these just be combined into their parent's
descriptionproperty? (Good examples for reference: the entirety of addons, Buffers and character encodings)
- Lingua principale
- JavaScript
- Stelle
- 65
- Fork
- 71
- Merge medio
- 4g 3h
- PR unite (30g)
- 31
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di nodejs/doc-kit
-
Difficoltà 2/5 Mezza giornata Idoneità per principianti 68/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 65/100
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
Tutte le issue di nodejs/doc-kit
Issue simili
-
bug confirmed issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
open-webui/open-webui#30750 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Mend: dependency security vulnerability untriaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100