fixStrictClassInitialization: Don't provide a default for string or number#24767
Merged
2 commits merged intoJun 7, 2018
Merged
fixStrictClassInitialization: Don't provide a default for string or number#247672 commits merged into
string or number#247672 commits merged into
Conversation
ghost
commented
Jun 7, 2018
| else if (type.flags & TypeFlags.Number) { | ||
| return createNumericLiteral("0"); | ||
| } | ||
| else if (type.flags & TypeFlags.Boolean) { |
Author
There was a problem hiding this comment.
Also have to change this since a foo | boolean union doesn't decompose to something containing boolean, it decomposes to boolean literal types.
mhegazy
approved these changes
Jun 7, 2018
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #24674 (comment)