feat: PathQuery depth #328
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
fominok
reviewed
Aug 20, 2024
Co-authored-by: fominok <[email protected]>
… feat/pathqueryDepth
fominok
approved these changes
Aug 20, 2024
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.
Issue being fixed or feature implemented
PathQuery depth is a small feature that gives the max depth of the PathQuery. This can be used to estimate the complexity of the PathQuery
What was done?
The PathQuery depth taxes the max of default pathquery subbranches and conditional pathquery subbranches.
How Has This Been Tested?
Added a test to check if it worked.
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only