Add a separate MF2 parser optimised for formatting#418
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The spec discussion and probable change in tc39/proposal-intl-messageformat#47 of requiring messages to be input as data models has highlighted the need for a performant parser. That's added here as
parseMessage(source, options). Its only supported option isprivateAnnotation, a function that can be defined to parse private^and&annotations.Unlike the CSV parser, this one does not create any intermediate structure on its way to the data model. It's also smaller, minifying & compressing to 2.3kB compared to the CSV's 4.4kB (The MessageFormat runtime is about 4.2kB).