Skip to content

Conversation

@mikz
Copy link
Contributor

@mikz mikz commented Jan 25, 2018

No description provided.

],
"version": "1.1",
"configuration": {
"$ref": "schema.json#"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@davidor I'd like to hear what is your though on this.

This would allow us to have schema and manifest in different JSON files, but we would need to use some tool (like json-refs) to merge the doc. It is not a big deal, just pass it through, I verified it works and creates correct output.

Or we can have the schema embedded in the manifest and have just one, bigger JSON.

]
},
"version": {
"$ref": "#/definitions/version"
Copy link
Contributor

@davidor davidor Jan 25, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why did you decide to extract this into its own definition and not do the same with description or name ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to try it out and I was expecting this might appear on multiple places, so defining a primitive for other validations.

@mikz
Copy link
Contributor Author

mikz commented Jan 26, 2018

Closing in favour of #565

@mikz mikz closed this Jan 26, 2018
@eguzki eguzki deleted the manifest-schema branch October 23, 2023 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants