Skip to content

Free up space in the TransformFlags enum #27410

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 1 commit into from
Oct 3, 2018
Merged

Conversation

rbuckton
Copy link
Member

@rbuckton rbuckton commented Sep 28, 2018

This PR frees up a few bits in the TransformFlags enum to allow room for more edition-specific flags. This is needed to support an ES2018 transform, such as in #26315.

It also contains a small fix for out up-to-date checks in the gulp builds, as they will break if we update LKG in master due to API changes.

const constructor = getFirstConstructorWithBody(node);
const hasInstancePropertyWithInitializer = forEach(node.members, isInstanceInitializedProperty);
const hasParameterPropertyAssignments = constructor &&
Copy link

Choose a reason for hiding this comment

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

Name no longer accurate

Copy link
Member Author

Choose a reason for hiding this comment

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

How is it no longer accurate? It is checking the same thing.

Copy link

Choose a reason for hiding this comment

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

I thought this would now trigger if any TS features were used inside it, not just parameter property assignments.

@rbuckton rbuckton merged commit a36e6e3 into master Oct 3, 2018
@rbuckton rbuckton deleted the freeUpTransformFlags branch October 3, 2018 19:39
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.

2 participants