fix(linter/prefer-class-fields): insert value after type annotation in fixer#15423
Conversation
ac51e73 to
622109b
Compare
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. |
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a bug in the unicorn/prefer_class_fields rule where it incorrectly placed value assignments when class properties had TypeScript type annotations. The fix now correctly inserts the value after the type annotation rather than after the property key.
- Updated the insertion logic to account for TypeScript type annotations when adding property values
- Added a test case to verify the fix works correctly with typed properties
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
622109b to
bcd0a57
Compare
Merge activity
|
bcd0a57 to
85bd19a
Compare
CodSpeed Performance ReportMerging #15423 will not alter performanceComparing Summary
Footnotes
|

Related to #14833