Enable i18n for placeholders and FieldDecorator messages among others
See original GitHub issueVersion
2.9.2
Environment
OS X, Chrome, React Intl
Reproduction link
https://github.com/enzolutions/antd-intl-demo
Steps to reproduce
$ git clone git@github.com:enzolutions/antd-intl-demo.git
$ npm run dev
$ npm run start
Open your browser at page http://127.0.0.1:8000/
You could see the input have a [object object] text inside as you can see in the following image

What is expected?
Field decorator message and input placeholder could be translated in the same way the Form Item label is translated
What is actually happening?
The translation object is not processed and the object type is rendered as string
I tried also with another i18n library https://github.com/vazco/meteor-universe-i18n with the same behavior.
The Antd library must be objected to enable those elements and similar accept object to enable a full translation
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Enable i18n for placeholders and FieldDecorator ... - Issuehunt
Enable i18n for placeholders and FieldDecorator messages among others #5866 ... have a [object object] text inside as you can see in the...
Read more >React i18n: A step-by-step guide to React-intl - Lokalise Blog
Adding arguments/placeholders; Building a locale selector in React i18n. Adding a wrapper; Rendering the language switcher.
Read more >Form - Ant Design
High performance Form component with data scope management. Including data collection, verification, and styles.
Read more >Textarea Usage - ServiceNow Developers
Text area input fields are used in forms and other use cases which require ... Required indicator: Field decorator that indicates if a...
Read more >Locale-specific message reference - Mozilla - MDN Web Docs
$placeholder_name$ (case insensitive) to insert a particular placeholder (for example $URL$ in the example above) into your string. $1 , $2 , $3 ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It is not a antd related problem.
You can’t use
<FormattedMessage />
in native input placeholder either, which only accept string type value.