We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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
standards-checklist/app/src/schema.json
Lines 44 to 47 in c22a4be
― #30 (comment)
The keys are a direct migration from the previous e.g.: standards-checklist/checklists/checklist.json Line 70 in f3418d9 "id": "bronze_doc_1", Which is now documentation.bronze.1. But I agree that these could be semi-informative short IDs instead.
The keys are a direct migration from the previous e.g.:
standards-checklist/checklists/checklist.json
Line 70 in f3418d9
Which is now documentation.bronze.1.
documentation.bronze.1
But I agree that these could be semi-informative short IDs instead.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
― #30 (comment)
― #30 (comment)
The text was updated successfully, but these errors were encountered: