-
Notifications
You must be signed in to change notification settings - Fork 82
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
Allow custom schema to be specified directly in annotation #610
Comments
Initial thoughts
|
I've provisionally added this to the 4.0 milestone, but we can decide not to do it and close it, or push it out of 4.0 if we're unsure or don't have time. |
Discussed on the call today, on balance we think it's probably a good idea, it provides access to all of the possible schema options and sidesteps the lack of recursion in Java annotations. We thought that an exception should probably be thrown at startup if the value is not well-formed JSON. However, we don't think we have enough time to add it in this release, though as it's just adding a new annotation parameter it would be a good candidate for a future minor release. |
What are your thoughts on having a
String value() default ""
property that could be used to set an arbitrary schema (that must be valid JSON/YAML)? That would give support for alternate dialects with the annotation.I'm not sure myself, but I wanted to mention it as a possibility.
Originally posted by @MikeEdgar in #601 (comment)
The text was updated successfully, but these errors were encountered: