-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
standards-checklist/app/src/schema.json
Lines 44 to 47 in c22a4be
"bronze": { "type": "object", "properties": { "1": {
I don't love using integer keys here, because
- the key doesn't have semantic relevance to the item
- I think the sequence of these items within a tier is arbitrary, but numbering them implies otherwise
- as the checklist evolves, we'd either end up with a sequence of numbers with gaps or reusing keys to mean different things across versions
The keys are a direct migration from the previous e.g.:
"id": "bronze_doc_1", Which is now
documentation.bronze.1.But I agree that these could be semi-informative short IDs instead.
Metadata
Metadata
Assignees
Labels
No labels