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.
Matching Order
Sometimes you want to make sure that individual parts of your query get executed in the right order. This is important for example if you use references in your query and need to make sure that the branches of the tree where those references are generated get visited before the branches that use them. Basically that means some parts of your code check have to be evaluated first. For example if you need to know the name of a certain object before checking whether this object gets used in the body of a function definition. For this, you can use the match_first special argument, which accepts a list of strings and makes sure that the corresponding key/value pairs in the match query will get checked in the order you provided. This is important if you work with references and want to make sure that the branch which stores the reference will get executed before the branch that makes use of it. An example: