Parametrize max depth #1
Merged
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
|
Had no idea this was a limitation.... Nice addition! Will test and merge next week |
|
Hey - just remembered I have this PR opened :) Did you have any time to take a look at it? |
|
I haven't had a chance to test (sry been crazy busy), but I'll go ahead and merge (I assume you've used this and it's working as expected). TY! |
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.
Sometimes you need to parametrize the max depth of the query. Here's a description of the issue I had and how I managed to solve it.
This PR adds the ability to control the depth of queries, how many relations will be extracted by a single query.