fix(macro): Ignore JSX comments when generating message ids#2434
Conversation
|
@maisano-patreon is attempting to deploy a commit to the Crowdin Team on Vercel. A member of the Team first needs to authorize it. |
|
@maisano-patreon thanks for fix, interesting why that wasn't reported before. note for myself - need to create the same test case in SWC repo. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2434 +/- ##
==========================================
+ Coverage 77.05% 81.21% +4.16%
==========================================
Files 84 104 +20
Lines 2157 2720 +563
Branches 555 725 +170
==========================================
+ Hits 1662 2209 +547
+ Misses 382 364 -18
- Partials 113 147 +34 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@andrii-bodnar i'm thinking of merging this to |
|
@timofei-iatsenko I agree, it would be nice to have this fix released in v5 |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Hey folks – any plans to merge this? |
andrii-bodnar
left a comment
There was a problem hiding this comment.
@maisano-patreon thanks for the contribution! My apologies for the delay 🙏
|
@maisano-patreon available in v5.9.1 |
|
@andrii-bodnar Thanks! Happy to contribute 🙂 |
Description
JSX comments like
{/* @ts-expect-error */}were consuming expression indices during message extraction, causing different hashes when comments were added/removed. I noticed this in a production build when compiling a Next.js application with@lingui/swc-plugin(which does not have this bug).Types of changes
Checklist