particle-os/particle-os-schema
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
31 commits 1 branch 0 tags 116 KiB
Find a file
Gerald Pinder 98d48fe2e1 fix: Have modules extend Module and we use a union of Module and CustomModule for module-v1
2024-10-13 19:15:17 -04:00
src-tsp fix: Have modules extend Module and we use a union of Module and CustomModule for module-v1 2024-10-13 19:15:17 -04:00
src-web refactor: split into src-web and src-tsp folders 2024-05-13 20:15:03 +03:00
.gitignore feat: fetch module schemas from blue-build/modules (#2) 2024-05-18 17:38:10 +03:00
.mise.toml feat: initial commit 2024-05-12 12:00:13 +03:00
buildWeb.js refactor: split into src-web and src-tsp folders 2024-05-13 20:15:03 +03:00
fetchModuleSchemas.js fix: Have modules extend Module and we use a union of Module and CustomModule for module-v1 2024-10-13 19:15:17 -04:00
justfile feat: add preprocess script for web output that corrects file paths 2024-05-13 19:53:07 +03:00
LICENSE feat: initial commit 2024-05-12 12:00:13 +03:00
package-lock.json chiore: update typespec 2024-08-08 17:38:50 +03:00
package.json chiore: update typespec 2024-08-08 17:38:50 +03:00
README.md chore: version recipe model 2024-05-13 20:45:07 +03:00
tspconfig.yaml chore: switch to json jsonschema 2024-05-12 12:16:30 +03:00

README.md

Schema

TypeSpec schema for BlueBuild.

Versioning

The recipe model uses a crude versioning scheme:_

  • The baseUri and filename of the recipe schema is recipe-vX.json
  • X is be the number of the version of the recipe format the model represents, starting at 1.
    • When a breaking change is made, the number shall be incremented by one. The old version should also be kept, with the previous version number, and in a separate file and model.
    • This number may be used to select which version of the standard to process in blue-build/cli