Fix JavaScript func_start regex to support Flow return types (#1755) - #1788
Merged
Conversation
Contributor
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
1 participant
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.
Fixes #1755.
This PR updates the JavaScript
func_startregex to properly support optional Flow-style return types (e.g.: void) before the=>in arrow functions and before the{in class/object-literal methods. This prevents valid Flow-typed functions from being silently ignored.It also updates
why_we_are_better_than_tree_sitter.mdto document GitGalaxy's superiority regarding tree-sitter error recovery hallucinations on React/Flow code (where tree-sitter incorrectly identifiesimportandletnodes as function declarations, while GitGalaxy gracefully handles them without parsing panic).