Scan functions inside of initializers or function calls#64
Merged
bobbylight merged 5 commits intoJun 18, 2025
Conversation
Contributor
Author
Contributor
Author
adbd9b6 to
93b57cd
Compare
Contributor
Author
|
I do not have intention working on this any further. I think even in current state it is an improvement and I suggest it to be merged as it is. |
Owner
|
Thanks for the PR! |
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.



Functions inside of initializers or function calls (and maybe in other positions as well) are currently ignored.
Such functions, passed as callbacks, are common is some JS enviroments.
First commit adds handling for functions defined in variable initializers, like this:
I hope to be able to handle at least following scenario as well: