fix(transformer/typescript): don't remove class fields without initializers when class-properties plugin is enabled#12771
Merged
graphite-app[bot] merged 1 commit intomainfrom Aug 3, 2025
Conversation
github-actions
bot
added
A-transformer
Member
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
CodSpeed Instrumentation Performance ReportMerging #12771 will not alter performanceComparing Summary
|
Member
Merge activity
|
…lizers when class-properties plugin is enabled (#12771) * close #12770 Both `typescript` and `class-properties` have the same transformation for class fields. They would conflict when both are run, so we have to stop transforming class fields in the `typescript` plugin when `class-properties` is enabled.
graphite-app
bot
force-pushed
the
08-03-fix_transformer_typescript_don_t_remove_class_fields_without_initializers_when_class-properties_plugin_is_enabled
branch
from
56fcd0a to
701399e
Compare
graphite-app
bot
deleted the
08-03-fix_transformer_typescript_don_t_remove_class_fields_without_initializers_when_class-properties_plugin_is_enabled
branch
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
undefinedwhentypescript.removeClassFieldsWithoutInitializer=true+assumptions.setPublicClassFields=true+target: 'es2021'and below #12770Both
typescriptandclass-propertieshave the similar transformation for class fields. They would conflict when both are run, so we have to stop transforming class fields in thetypescriptplugin whenclass-propertiesis enabled.