-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Please increase schema length constraint more than 51200 chars #551
Comments
If you have larger schemas it's best to use one of the plugins to generate code (CLI, Maven, Gradle). The website isn't really there to process large amounts of data. |
Thank you Joe.
|
I'm trying to generate a pojo from a larger schema via a gradle task, and unfortunately I'm having issues generating. For files with 51k characters and less the gradle task works, so I know I configured it correctly. For the large file the gradle build is successfull, however I don't get the generated output. Is there something I am missing in my build.gradle file?
The schema in question is this adaptive-card.json file from Microsoft (unfortunately there isn't a java SDK for Adaptive Cards). Thank you! |
I don't know if any limit when using the gradle plugin. The limit only applies to the online generator at jsonschema2pojo.org. Do you see any errors? |
No errors. The build is successful however there is no output. The adaptive card schema version 1.1.0 works, however I suspect it's because that schema is significantly smaller (1.1.0 also generates on jsonschema2pojo.org). Also the flags --info and --debug are quite unhelpful and don't signal any errors |
It seems that referred schema v. "definitions": {
...
},
"anyOf": [{
"allOf": [{
"$ref": "#/definitions/AdaptiveCard"
}
]
}
] Note that at present jsonschema2pojo does not process
|
I have a large schema which is more than 51K chars. While generating pojo's using this schema I am getting below length constraint.
There's a problem: Your input was larger than 51200 characters, try making this a bit smaller.
Could you help me out to execute my large schema.
The text was updated successfully, but these errors were encountered: