-
Notifications
You must be signed in to change notification settings - Fork 40
Auto generate Kedge JSON schema for every PR #280
Comments
we could use Bintray for hosting JSON schema similarly to what we are doing with latest builds We should have JSON schema for every release and one for the latest (corresponding with master branch) |
@kadel That does make sense to me. Except that I would rather call |
you are right, 'master' is much better |
Documentation on how json-schema generation works and describing generated files as part of this issue. |
@kadel marked it! |
Right now blocked on instrumenta/openapi2jsonschema#5 Will have to debug our OpenAPI maybe if that is causing problems! |
I think our JSON Schema is in a better and workable state right now. All that's left is to do the generation on every merge and push to https://github.com/kedgeproject/json-schema automatically. |
This commit configures Travis to run a script on every merge to Kedge master branch which updates the JSON Schema residing in https://github.com/kedgeproject/json-schema Significantly improves kedgeproject#280
This commit configures Travis to run a script on every merge to Kedge master branch which updates the JSON Schema residing in https://github.com/kedgeproject/json-schema Significantly improves kedgeproject#280
This commit configures Travis to run a script on every merge to Kedge master branch which updates the JSON Schema residing in https://github.com/kedgeproject/json-schema Significantly improves kedgeproject#280
On every merge of PR we need to update the JSONschema for kedge, right now the JSONSchema resides in https://github.com/kedgeproject/json-schema/tree/master/schema Right now it is done manually, we need to automate it.
So two things need to be done right now:
The text was updated successfully, but these errors were encountered: