feat: produce comment and context in transform output#201
Merged
andrii-bodnar merged 1 commit intomainfrom Feb 25, 2026
Merged
Conversation
andrii-bodnar
approved these changes
Feb 25, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #201 +/- ##
==========================================
+ Coverage 92.61% 92.69% +0.08%
==========================================
Files 8 8
Lines 1448 1465 +17
==========================================
+ Hits 1341 1358 +17
Misses 107 107
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
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
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.
This is a follow up for #193
Related #190
I found that original implementation doesn't produce
contextandcommentfields (because it was never supposed to be used with extractor, so that was a simplicfication i made), so the result of swc plugin transformation could not be directly used with lingui extractor as user wanted.This adds this functionality and make it behave closer to the js version - in fact, exactly as a js version.
fyi @karmeleon