Is there a way to force a decimal separator for useNumberField/NumberField? #5422
-
|
I'm currently using I checked the documentation for the hook, component and also the MDN documentation for Intl.NumberFormat but couldn't find a definitive answer. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
|
Given that lat/long coordinates really shouldn't be localized, as near as I can tell https://ux.stackexchange.com/questions/85702/localizing-coordinates You could pass the locale When you move to the component, you can wrap it in the i18n provider https://react-spectrum.adobe.com/react-aria/internationalization.html |
Beta Was this translation helpful? Give feedback.
-
|
Fair enough, probably asking too much. 😅 Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Sorry to post again, but I noticed it's rounding up numbers ending with zeros, say for example |
Beta Was this translation helpful? Give feedback.
-
|
Should be able to specify a minimum number of decimal places https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat/NumberFormat#minimumfractiondigits A few things to keep in mind, if you don't need the step value, don't need localization to anything other than English, or need more decimal places than the formatter can handle, then you might be better served by a text field with your own validation. These numbers seem to be quite a special case. |
Beta Was this translation helpful? Give feedback.
-
|
I had a look at how far you actually need to represent lat/long in terms of fraction digits https://gis.stackexchange.com/questions/8650/measuring-accuracy-of-latitude-and-longitude We support up to ~18 fraction digits (thanks JS), so I think you'll be fine. https://codesandbox.io/s/vigorous-fast-p5p28w?file=/src/App.js |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Yeah, I was thinking that using TextField with my own validations would be more ideal, I'll work on that. |
Beta Was this translation helpful? Give feedback.
Given that lat/long coordinates really shouldn't be localized, as near as I can tell https://ux.stackexchange.com/questions/85702/localizing-coordinates
You could pass the locale
'en-US'to the hook. Then it would always have a decimal and shouldn't cause a problem because it shouldn't be localized to anything else.When you move to the component, you can wrap it in the i18n provider https://react-spectrum.adobe.com/react-aria/internationalization.html