Language property for better localization support #1331
fredericbahr
started this conversation in
Ideas
Replies: 1 comment
-
@KevinVandy could you please shortly share your opinions on that. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there,
first off, thank you for this fantastic library! It's packed with a lot of useful features that make development a breeze.
One standout feature is the ability to provide localizations for different languages. However, I noticed a limitation when it comes to fully supporting localization in a multi-language app. Specifically, while the library uses
Number.toLocaleString
in certain places (e.g., default pagination), it's challenging to update the number formatting when switching languages. Currently, changing the language only updates texts, but not the numeric formatting.To address this, I propose introducing a new property language which would accept a language code compatible with Number.toLocaleString. This property could then be passed down wherever Number.toLocaleString is used, ensuring consistent number formatting in multi-language applications.
If this idea aligns with your vision for the library, I’d be happy to contribute by submitting a PR with the necessary changes. I believe this enhancement would greatly improve localization support and benefit many users.
Looking forward to your thoughts!
Beta Was this translation helpful? Give feedback.
All reactions