-
Notifications
You must be signed in to change notification settings - Fork 35
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
Json is represented as "type": "object" #303
Comments
The produced JSON Schema didn't allow arrays as an input for a JSON type. fixes #303
### [1.6.1](v1.6.0...v1.6.1) (2022-01-25) ### Bug Fixes * Generated JSON type allows arrays ([7ae084a](7ae084a)), closes [#303](#303) ### Dependencies and Other Build Updates * fix semantic release ([27cab5c](27cab5c)) * Fix semantic release ([4c46e26](4c46e26)) * fix semantic-version release ([e7ae2b2](e7ae2b2)) * **deps-dev:** Add missing conventionalcommits dependency ([fe9c86b](fe9c86b)) * Automatically build release for dependency updates ([163befb](163befb))
🎉 This issue has been resolved in version 1.6.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@capaj Thank you for reporting this! The Issue is resolved and should be fixed now :) |
@valentinpalkovic oh thank you for being able to jump on this so fast. I just wish I had realized sooner, that a valid JSON is also scalar values like string, null or a number, so the generated type here should really be: "type": ["number", "string", "boolean", "object", "array", "null"] sorry for that. I mostly use graphql these days, so I forgot how to properly do |
@capaj No problem! :) I just wanted to discuss with you, whether it makes sense to define the type without Required case:
Not required:
I know, that per definition the JSON type is allowed to also be What do you think? (See #305) |
yes, I do think null is to be expected. |
Alright! I will adjust my MR tomorrow and I will release a new version afterwards! I will let you know. |
### [1.6.2](v1.6.1...v1.6.2) (2022-01-26) ### Bug Fixes * Add more valid types for JSON type ([3ead22c](3ead22c)), closes [#303](#303)
🎉 This issue has been resolved in version 1.6.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
It should be generated as
it is generated as
The text was updated successfully, but these errors were encountered: