Skip to content

Update normalizeClassDefinition.js #273

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

Merged
merged 2 commits into from
Jun 7, 2018
Merged

Update normalizeClassDefinition.js #273

merged 2 commits into from
Jun 7, 2018

Conversation

jquense
Copy link
Collaborator

@jquense jquense commented Jun 7, 2018

Should i submit this against v3-dev? I meant too originally

Copy link
Collaborator

@danez danez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please add a test? Otherwise looks good.

PR against master is fine, I just cherry pick after merge.

@jquense
Copy link
Collaborator Author

jquense commented Jun 7, 2018

I wrote the test in a way the works in v1. I realized that i've not noticed this before because it seems like bablyon has only recently started making these ClassDeclarations, in the past they were expressions

@danez
Copy link
Collaborator

danez commented Jun 7, 2018

Yeah it probably does not happen in v2 but does happen in the v3 beta. But good to have the check anyway.

Thank you very much.

@danez danez merged commit 9e4f3f4 into master Jun 7, 2018
@danez danez deleted the fix-class-decl branch June 7, 2018 14:56
danez pushed a commit that referenced this pull request Jun 26, 2018
* Update normalizeClassDefinition.js

* add test
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants