tc39 / proposal-intl-messageformat

TC39 Proposal for Intl.MessageFormat

https://tc39.es/proposal-intl-messageformat

tc39/proposal-intl-messageformat Issues

Normalize type checking in the spec text
Updated 4 months ago1
Avoid methods in MessageValue
Updated 4 months ago3
Ready for Stage 2?
Closed 4 months ago9
Normalize the representation of the `:number` and `:string` functions
Updated 4 months ago
Too much object created
Updated 5 months ago1
What are the types of MessageFunction's argument and option values?
Updated 5 months ago1
Semantics of locales argument to MessageFormat
Updated 5 months ago8
Locale should be the first argument
Updated 8 months ago2
Return Iterable<MessagePart> from toParts
Updated 9 months ago1
Replace "would resolve to" with abstract operations
Updated 9 months ago
MessageValue should not have a locale property
Updated 9 months ago
Make MessageValue subclassable and allow passing it as input variables
Updated 9 months ago
Consider making it possible to evaluate strings like tagged template literals
Closed a year ago2
Message resource handling should be split into a separate proposal
Closed a year ago
Consider immutable Records for message resources
Closed 2 years ago
Separate endpoints for parsing single messages & message resources
Closed 2 years ago
What problem does this solve?
Closed 2 years ago1
Method naming
Closed 2 years ago4
Use of `resId` in `format/formatToParts`
Closed 2 years ago1