FormattedPlural support about babel-plugin-react-intl HOT 4 CLOSED

Sorry, solved with this comment formatjs/formatjs#162 (comment)

from babel-plugin-react-intl.

@bardt does this distinction between <FormattedPlural> and <FormattedMessage> make sense to you? The addition of <FormattedPlural> was to expand React Intl to be useful for single-language apps too.

An interesting aspect of you brining this up is that if someone is using this Babel plugin, then they shouldn't be using <FormattedPlural> because it means they likely have hard-coded strings in they're app that won't be extracted for translation. So the plugin could be updated to warn when it encounters a <FormattedPlural> declaration… what do you think?

from babel-plugin-react-intl.

@ericf right now I see an inconvenience, probably caused by changes in react-intl v2, between official docs, v2 tread instructions and this plugin. It took some hours of experimenting to finally get it working like I supposed it to. I'd definitely vote for better developer experience we are used to in React itself (meaningful warnings, suggestion of using react devtools extension etc.).

Right now I'm close to a big deadline on a project I'm trying to use react-intl on, so have no spare time. After that, I could help with some changes to this plugin, according to my own dev experience.

from babel-plugin-react-intl.

@bardt no worries, I'm happy to add in this warning. Feel free to ping me if you run into any other issues as you work towards your deadline!

from babel-plugin-react-intl.