fix(parser): support parsing expressions in extend clause #409
Conversation
Thanks |
What should this PR allow? I didn't see any change in my web component docs which are using mixins using a different approach. Should this PR allow the identifications of mixins when implemented such as these techniques?
or a Composable implementation
|
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.
Currently esdoc fails for code containing a call expression in 'extends' clauses which is a supported feature and is popular with mixins.
Failing code: