fix: Unhandled CallExpression expression syntax: CallExpression #255
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
d3xter666
approved these changes
Aug 12, 2024
d3xter666
previously approved these changes
Aug 12, 2024
matz3
force-pushed
the
fix-callexpr-on-callexpr
branch
from
b3f6a8b to
b0a1cb6
Compare
CSSSize is already detected
d3xter666
approved these changes
Aug 12, 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.
A CallExpression on a CallExpression wasn't handled yet and caused a
fatal error.
This commit also adds a test case for another issue that was already
fixed via #73 (SuperKeyword).
Fixes: #246