-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
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
systemservices/marketplace: manifest validation #829
Conversation
e4480c6
to
35ff845
Compare
2ca13c3
to
47d6a3f
Compare
Just seeing this PR I was thinking why not delegating more to the system service and have the publish command that actually take the content of the manifest in the |
47d6a3f
to
7d12df8
Compare
77ed536
to
70ada3e
Compare
manifest data is created by users/devs. thus, its content is not trusted and it needs to be validated. this way, it's possible to ignore any service versions that have invalid manifest data. the validation made with JSON Schemas, one created from Manifest TS type and other created manually for service's definition. * added gen-schema command to package.json to generate JSON Schema of Manitest type. * added package-lock.json file.
5146c90
to
ea6f8ec
Compare
…github.com/mesg-foundation/core into ss-marketplace/feature/manifest-validation
…tplace/feature/manifest-validation # Conflicts: # systemservices/marketplace/package-lock.json # systemservices/marketplace/package.json
manifest data is created by users/devs. thus, its content is not trusted and it needs to be validated. this way, it's possible to ignore any service versions that have invalid manifest data.