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
A ways off, but something we should potentially support in the future. intlc will likely still provide a superior experience than plain JS/TS as with ICU especially for type safety.
This may mean adding a new key to each message specifying the format type. We may consider calling it "input" and renaming "backend" to "output". And/or it might mean supporting a new input format entirely alongside JSON.
The text was updated successfully, but these errors were encountered:
https://github.com/tc39/proposal-intl-messageformat
A ways off, but something we should potentially support in the future. intlc will likely still provide a superior experience than plain JS/TS as with ICU especially for type safety.
This may mean adding a new key to each message specifying the format type. We may consider calling it "input" and renaming "backend" to "output". And/or it might mean supporting a new input format entirely alongside JSON.
The text was updated successfully, but these errors were encountered: