Implement configuration options to limit depth of certain fields on s…#49
Open
paulwellnerbou wants to merge 2 commits into
Conversation
…erver site to avoid too much data if using a lot of relations and/or parent-child relations
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Implement configuration options to limit depth of certain fields on server site to avoid too much data if using a lot of relations and/or parent-child relations.
This may break previous usages, as the protection for recursion is removed. This did not work in my case, as there was data excluded that had the same name, but different paths.
To avoid recursion, this has to be configured now using one of the new configuration options, either
ignore, to completely ignore a certain field, orfields, to hard limit the depth of certain collections and fields.