Skip to content
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

fix: hoist statement counter for class variables #60

Merged
merged 1 commit into from May 21, 2017

Conversation

novemberborn
Copy link
Contributor

With const foo = class {}, foo.name should be 'foo'. Without this commit the instrumentation causes foo.name to be an empty string.

Hoist the statement counter just like it's done for function and arrow expressions. Fixes #59.

With `const foo = class {}`, `foo.name` should be `'foo'`. Without this
commit the instrumentation causes `foo.name` to be an empty string.

Hoist the statement counter just like it's done for function and arrow
expressions. Fixes #59.
@bcoe
Copy link
Member

bcoe commented May 21, 2017

@novemberborn great work 👍 thanks for diving into this.

@bcoe bcoe merged commit 120d221 into master May 21, 2017
@bcoe bcoe deleted the hoist-class-statement-counter branch May 21, 2017 22:46
@bcoe
Copy link
Member

bcoe commented May 27, 2017

@novemberborn this is now landed and available in nyc@next -- mind testing and making sure everything runs well for you?

@novemberborn
Copy link
Contributor Author

@bcoe going by novemberborn/function-name-support#2 the failing AVA tests are now passing, which implies the instrumentation is no longer interfering. I haven't had a chance yet to actually update the test code though.

@novemberborn
Copy link
Contributor Author

Works great @bcoe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants