Re-export public_ext from generated LocaleKeys file#786
Conversation
Closes aissat#780. Adds `export 'package:easy_localization/src/public_ext.dart';` to the generated file's header. Consumers that already import the generated `locale_keys.g.dart` (e.g. `import 'generated/locale_keys.g.dart';`) now also pick up the `Text.tr()` / `Text.plural()` extensions without a second `import 'package:easy_localization/easy_localization.dart';` line — eliminating the two-import requirement called out in the issue.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe generator now adds an export directive for Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
Closes #780.
Adds
export 'package:easy_localization/src/public_ext.dart';to the generated file's header. Consumers that already import the generatedlocale_keys.g.dart(e.g.import 'generated/locale_keys.g.dart';) now also pick up theText.tr()/Text.plural()extensions without a secondimport 'package:easy_localization/easy_localization.dart';line — eliminating the two-import requirement called out in the issue.Summary by CodeRabbit