-
Notifications
You must be signed in to change notification settings - Fork 390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: remove withI18n #1503
feat: remove withI18n #1503
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
size-limit report 📦
|
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## next #1503 +/- ##
==========================================
+ Coverage 73.93% 73.99% +0.06%
==========================================
Files 67 67
Lines 1872 1865 -7
Branches 493 491 -2
==========================================
- Hits 1384 1380 -4
+ Misses 383 382 -1
+ Partials 105 103 -2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
Totally agree with you. Also thought about that, but working on tooling was my first priority, because there were more pain points. I think it's something very old and in new projects it's just enough to use |
@vonovak could you also add a note in the migration guide ( |
@vonovak thank you for the contribution! |
Description
Feel free to close this, but since there will be a new major I thought withI18n could be removed
For new projects, having a HOC doesn't make much sense
For old project, they can add the HOC to their code base
For the library, it means one less thing to worry about (for example I remember typing HOCs was a pain, although that was a looong time ago), smaller api surface.
Types of changes
Fixes # (issue)
Checklist