Skip to content

Free up space in the TransformFlags enum#27410

Merged
rbuckton merged 1 commit intomasterfrom
freeUpTransformFlags
Oct 3, 2018
Merged

Free up space in the TransformFlags enum#27410
rbuckton merged 1 commit intomasterfrom
freeUpTransformFlags

Conversation

@rbuckton
Copy link
Copy Markdown
Contributor

@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 hasParameterPropertyAssignments = node.transformFlags & TransformFlags.ContainsParameterPropertyAssignments;
const constructor = getFirstConstructorWithBody(node);
const hasInstancePropertyWithInitializer = forEach(node.members, isInstanceInitializedProperty);
const hasParameterPropertyAssignments = constructor &&
Copy link
Copy Markdown

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
Copy Markdown
Contributor 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
Copy Markdown

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
@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 21, 2025
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