{{ message }}
Repository navigation
Conversation
thePunderWoman
added
action: merge
Future changes to initialization order can cause this previously OK code to start having compiler erroring like: `TS2729: Property 'foo' is used before its initialization.`
thePunderWoman
force-pushed
the
patch-1
branch
from
February 19, 2025 22:10
7831b4f to
d3325cc
Compare
Contributor
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.
3 participants
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.
Future changes to initialization order can cause this previously OK code to start having compiler erroring like:
TS2729: Property 'foo' is used before its initialization.PR Checklist
Please check if your PR fulfills the following requirements:
Not relevant for missing items.
PR Type
What kind of change does this PR introduce?
What is the current behavior?
If you enable
tsc--target=ES2022and--useDefineForClassFields, will result in aTS2729` compilation error.Issue Number: N/A
What is the new behavior?
No compilation error with the previous flags.
Does this PR introduce a breaking change?
Other information