-
-
Notifications
You must be signed in to change notification settings - Fork 1k
feat(locale): add word data to pt_br and pt_pt locales #3531
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(locale): add word data to pt_br and pt_pt locales #3531
Conversation
✅ Deploy Preview for fakerjs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @DanielShvarts2004 👋 The tests in the pipeline are failing, because the locale data you provided contain duplicate values. Can you remove them? If you need help with anything, feel free to ask :) |
|
Hey thank you for your helpful response 🙏 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #3531 +/- ##
==========================================
- Coverage 99.97% 99.97% -0.01%
==========================================
Files 2880 2888 +8
Lines 220510 222112 +1602
Branches 951 952 +1
==========================================
+ Hits 220457 222053 +1596
- Misses 53 59 +6
🚀 New features to boost your workflow:
|
xDivisionByZerox
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes itself look fine. Would you be able to sort the list alphabetically? 🙂
We already introduced sorting in some locale data, but not in the work module so far. By sorting the data now you'd help us reduce the potential diff when we introduce the normalization later this year.
|
Of course! Love the idea |
|
I don't know how similar pt_PT and pt_BR are. Could we use the same word lists for pt_PT? |
|
@matthewmayer (If we would do that, why do we need them both and not expose one pt locale?) |
We need both because for example the location or phone modules are substantially different for both. Maybe could copy over and then we could make tweaks to the pt_PT version in future if there are any words which are uncommon in pt_PT. |
|
You're right, good point. I'll do that. |
e587f4f
|
Thank you for your contribution @DanielShvarts2004 🙏
|
|
Resolves #3521