Adding support to extract messages from intl.formatMessage calls #39
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.
What: Posible implementation for #38 feature request
Why: Without these changes, Users can't generate locale ids and messages that are used in
intl.formatMessagefunction calls as direct object argument.i:e
Above id (Supported.file.type) and message will not be available in generated locale file, Unless
extractFromFormatMessageCallis set to true inbabel-plugin-react-intlplugin configurations.How: Changes were done to pass the
extractFromFormatMessageCallparameter tobabel-plugin-react-intlconfigurations via theextract-react-intllibrary interfaces.So that this PR depends on: akameco/extract-react-intl#21
Checklist: