-
-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instrumented code for code coverage is not getting parsed correclty #571
Comments
@hiaux0 there @hiaux0 there are existing tests here validation/test/property-accessor-parser.ts Lines 47 to 54 in 862da07
It seems the fix is already figured out, can you help create a PR with some tests @hiaux0 ? |
Afai can see, it fixes just for normal properties, and not methods, ie. - __gen$field.f[\'10\']
+ __gen$field().f[\'10\'] // I'm expecting `()`
yeah, I planned to when I find some spare time |
bigopon
pushed a commit
that referenced
this issue
Feb 2, 2023
* fix: property accessor ignore instrumenter This supports instrumentation code from @jsdevtools/coverage-istanbul-loader. Fixes #571 * cleanup --------- Co-authored-by: Pal, Sayan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#547 addresses a related issue.
(other related: aurelia/testing#94)
Problem
What I found, is that the instrumented code (maybe special to this lib
@jsdevtools/coverage-istanbul-loader
) is using methods instead of simple propertiesSuggested fix
A fix I found is to update the parts of the regex by including
()
(open and close paren)Keywords:
@jsdevtools/coverage-istanbul-loader
code coverage instrumented code
The text was updated successfully, but these errors were encountered: