New and improved CallResolver
#773
Closed
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
oxisto
force-pushed
the
fix-call
branch
2 times, most recently
from
5a1a8c9 to
f39df82
Compare
oxisto
force-pushed
the
fix-call
branch
2 times, most recently
from
ae17a74 to
a9587c5
Compare
oxisto
changed the title
CallExpression and MemberCallExpressionCallResolver
This PR restructures the way call expressions and member call expressions work. It introduces a new `callee` field, to allow modelling of calls that were previously not possible (see #689) and also reworks the way, the `base` property works. This IS API breaking and will probably the first PR that starts the v5 development. Fixes #689 Fixes #289
|
|
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.
This PR restructures the way call expressions and member call expressions work. It introduces a new
calleefield, to allow modelling of calls that were previously not possible (see #689) and also reworks the way, thebaseproperty works.This IS API breaking and will probably the first PR that starts the v6 development.
Fixes #689
Fixes #298
Fixes #704