-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
Locales Support #1
Comments
I can check this. |
✅ Closes: ngneat#1
I saw PR related to this issue. That's very cool that we can use Google Translate to translate. But in terms of library API, how this will work taking into consideration that needs to be tree shakeable? 🤔 import { locale } from '@ngneat/falso'
// Something like this?
locale('en') or maybe we can generate per locale bundles? 🤔 import { randomWord } from '@ngneat/falso/de'
randomWord() or we can make everything that is not translateable to be imported from I like more this third option |
Yes, the next step should be the third option using second entry points. |
✅ Closes: ngneat#1
✅ Closes: ngneat#1
✅ Closes: ngneat#1
✅ Closes: ngneat#1
@theryansmee do you think you can handle this? |
@NetanelBasal - Sorry I don't have any experience with this. It would probably be better suited for someone else. |
What would be the approach here. Using fileReplacements or ENV properties to replace default locale e.g. Wouldn’t it be better for functions that need locales, to group them in own folder?
|
We don't want it as a separate npm package. The goal is to import it as:
|
Exactly, but each locale subfolder will be a completely different build 🤔 |
Yes, but they will be imported from the main package |
yes |
I started to work on it. Would provide a draft PR over the weekend. 😊 |
Hi I am sorry but the only random value exported from locales seems to be "randomBird". Is this right? |
Description
Add locales support
Proposed solution
Generate data via google translate?
Alternatives considered
?
Do you want to create a pull request?
No
The text was updated successfully, but these errors were encountered: