"How complexity scoring works" guide #4790
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
gmac
commented
Jan 17, 2024
| @@ -10,6 +10,46 @@ index: 4 | |||
|
|
|||
| GraphQL-Ruby ships with some validations based on {% internal_link "query analysis", "/queries/ast_analysis" %}. You can customize them as-needed, too. | |||
|
|
|||
| ## Prevent deeply-nested queries | |||
There was a problem hiding this comment.
Moving depth up so to keep complexity topics next to each other.
gmac
force-pushed
the
patch-1
branch
6 times, most recently
from
0029054 to
5f4f524
Compare
|
Thanks for writing this up! |
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.
A frequent source of confusion internally. This summarizes the nuances of the complexity scoring process for the benefit of all.