-
-
Notifications
You must be signed in to change notification settings - Fork 919
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 lorem for uz_UZ_latin #2824
Conversation
✅ Deploy Preview for fakerjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #2824 +/- ##
==========================================
- Coverage 99.96% 99.95% -0.01%
==========================================
Files 2975 2977 +2
Lines 214451 215466 +1015
Branches 602 949 +347
==========================================
+ Hits 214366 215377 +1011
- Misses 85 89 +4
|
What could be the root cause for the failing unit test: test/scripts/apidocs/verify-jsdoc-tags.spec.ts > verify JSDoc tags > phone > number > 0 > verify @example tag |
We are currently analyzing the problem with the CI pipeline (see #2782). For now, any team member has to restart failed jobs. Sorry for the inconvenience :( It's definitely not on your side, tho. |
@ST-DDT can I ask you to perform code review? |
I'm currently busy, I'll review it when I have time. |
The English (well really fake Latin) words in lorem definitions are lowercase. Maybe do the same? |
It looks like Uz also has uppercase words, so IMO lorem can also contain them. |
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 words itself look fine, but IMO the purpose of lorem
is creating a text that is not supposed to be read. So en and de use Latin for that. Why did you use actual words?
(Or is it just google translate that assigns a translation to them even though they don't have any?)
If the intent is to use actual lorem I can change it though I was looking to Russian locale as an example and there were proper words, that's why I used the same approach. I thought these words could be used to generate some comments, messages etc. However, if you think it's better to keep it consistent I will do so :) |
My feeling is that most languages that use the Latin alphabet should probably just stick to the fake-Latin lorem so they don't need a locale-specific version of lorem. If you want "real" words you should use the word module. |
Sounds reasonable. Should I copy the words from Latin locale then into Uzbek? Or should I take it from somewhere and export it from Uzbek locale? |
You probably don't have to do anything. All locales currently fall back to en and en already has the Latin lorem definitions. |
Team Decision
|
Sorry for the late fix. I copied words should I update the docs and create new PR for that? |
All good, no worries. The only thing you need to do is the bullet point one as you did in your latest commit f681ef6. The other bullet points are for us, the faker team, to remember certain decisions made. |
If it is identical to import words from '../../en/lorem/words';
export default words; |
I also considered this, but we could also do that in the mentioned cleanup PR. |
I'd suggest moving this to a separate PR as well. This way we can take the time to investigate if this is somehow influencing tree shaking for specific localized faker instances. I'd prefer to leave this kind of work to the faker team. |
I created a separate issue for the team todos: Thank you @Mirazyzz for your contributions ❤️ |
@ST-DDT Thank you for constantly providing constructive feedback, it's a pleasure to contribute to your community and project. I myself enjoy using faker library and to planning to contribute more in the future! |
No description provided.