perf(linter): update prefer-node-protocol to use diverging match#14699
Merged
graphite-app[bot] merged 1 commit intomainfrom Oct 17, 2025
Conversation
This was referenced Oct 17, 2025
Merged
Member
Author
CodSpeed Performance ReportMerging #14699 will not alter performanceComparing Summary
Footnotes
|
camc314
approved these changes
Oct 17, 2025
Contributor
Merge activity
|
…14699) Diverging match is recognized by the linter codegen, so adding the `return` here enables node type analysis.
55494f9 to
07db921
Compare
a7c62b1 to
2fe9dfa
Compare
Base automatically changed from
10-16-perf_linter_update_catch-error-name_to_use_top-level_match
to
main
October 17, 2025 10:45
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
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.

Diverging match is recognized by the linter codegen, so adding the
returnhere enables node type analysis.