You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As for module-specific docs, I think those would only have to mention ECMA-402 when formatter instances are passed as arguments, as those don't need to be Globalize formatters.
As for module-specific docs, I think those would only have to mention ECMA-402 when formatter instances are passed as arguments, as those don't need to be Globalize formatters
(I am currently planning our approach of i18n+l10n for a mid-size SPA and did only find this ticket searching exactly the proposed addition to the docs)
Is the approach from the Example compatible with the globalize-compiler?
What are the non-trivial cases of using this? Date was mentioned and I presume Message is impossible at the moment.
Edit: Nvm guys; found out formatjs uses those by default and our team should be able to work around the different structure of the message parser integration over there. Keep up the good work!
We should provide examples demonstrating how certain modules (e.g., message, relative time, unit formatters) could be used along with Ecma-402.
💥 It's important to highlight that such mixture of libraries will decrease the supported browsers (or will require user to polyfill when needed).
I think this topic deserves presence in the main documentation (REDAME.md) and specific examples inside of each of the mentioned modules.
Requires:
Examples:
Ref #399
The text was updated successfully, but these errors were encountered: