Disable the class fields transform when disableESTransforms is set #625
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.
When disableESTransforms is specified, the class transform can almost entirely
be skipped, but we still need to do some work:
readonly
orprivate
) need to be transformed to assignments within the constructor.declare
need to be removed. Uninitialized fields not markeddeclare are preserved, matching the ES spec and the
useDefineForClassFields
flag in TS.
For now, we still use the
getClassInfo
code path but give alternate results.In the future we can hopefully simplify that code path, and possibly change
declare
parsing so the whole line consists of type tokens that will naturallybe erased.