final-form/react-final-form

I18n example needed

Open

#568 opened on Jul 22, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (7,316 stars) (510 forks)batch import
help wanted

Description

Would love to see an example on how best to approach i18n, e.g. with react-i18next or other. Where's the best place to hook into to localize all field labels and error messages, regardless if they come from Field or custom component (if that's possible).

Contributor guide

Tech stack
javascriptreact
Domain
frontenddeveloper experience
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic React knowledgeUnderstanding of react final form
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Check the existing examples directory (e.g., /examples) in the react final form repository to understand the format and conventions used. Review how other examples are structured and linked in documentation. Consider integrating react i18next or a similar library to localize field labels and error messages. The example should demonstrate hooking into the form's validation and render props. Look at the comments in issue #568 for any additional context or specific requests from maintainers.