Fair. But we know this via the same inputs that are used to render it. They are required, otherwise we cannot present.

Three things needed are:

1. Value
2. Format
3. Locale

Nothing else right?

With input you also need to ability to accept partial number/result, e.g 100. and with the combination of options it's still fairly hard. TBH I don't know of anything off the shell to parse a string even given a format. It's not a 1-1 mapping, as in 1 output can come from many numbers + formats.

Sure, but let's say we know the format.

Use case:

• data is stored in format A.
• data is presented in a localised format, set by an i18n file, supporting the locale of choice.
• the locally presented data is in a form input
• the input data can be modified by a user
• onChange/onUpdate/onSubmit that needs to be converted back (we do know the locale + format used, and we do know the new value)

So while what you say is absolutely true, we're not attempting to divine the format. Looking for a confirmation of the above three things given the example provided.

yeah sorry I'm not aware of any out-of-the-box solution for that :(