Skip to content
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

If schema would be too large, strip titles to reduce size #323

Open
azaroth42 opened this issue Feb 12, 2025 · 0 comments
Open

If schema would be too large, strip titles to reduce size #323

azaroth42 opened this issue Feb 12, 2025 · 0 comments
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@azaroth42
Copy link

Is your feature request related to a problem? Please describe.

In order to avoid the recursive schema issue #319, we can materialize the hierarchy. However, this quickly runs into the maximum schema length test, even without enums, dates or even property names longer than 1 character. A way to reduce the size would be to strip title from every property if that would reduce the size to within acceptable limits.

Describe the solution you'd like
If the schema would generate the "too many states for serving" error, then delete all title definitions from properties.

Describe alternatives you've considered
Fixing #319 :)

@azaroth42 azaroth42 added priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. labels Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

1 participant