Increase limit on contentType query to maximum (1k) #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Great! I'll release a patch version for you today |
|
Released in v0.2.12 |
|
Thank you @gburgett, appreciate it!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We currently have an environment that is approaching >100 content types - Using
contentful-ts-generator, the resulting schema/type definitions are omitting content types after that 100 limit is reached.As per Contentful, the default limit on these queries is
100and the maximum allowed limit is1000. This PR defineslimit: 1000in the opts forgetContentTypesin order to surpass the default100limit and to avoid environments with >100 content types from receiving omitted type definitions.