-
-
Notifications
You must be signed in to change notification settings - Fork 794
Adding Support for Localization of Error Messages #1304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While I agree with the intent of the PR, the impl. could be a bit more generic.
How about we allow customizing all the messaging (harcoded strings) instead, then let the user do what they please with these messages (e.g. apply i18n).
That might be a good idea!Can you give me some more specific steps? |
I think a property that can be set on the hook could work.
This could be a func, e.g. `errMsg(key: string) string`, that gets called
to get the err msg for a given key, or some object with static msg
definitions.
…On Sat, Oct 5, 2024, 06:11 hatsu ***@***.***> wrote:
@rolandjitsu <https://github.com/rolandjitsu>
How about we allow customizing all the messaging (harcoded strings)
instead, then let the user do what they please with these messages (e.g.
apply i18n).
That might be a good idea!Can you give me some more specific steps?
—
Reply to this email directly, view it on GitHub
<#1304 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALJIOMR6XUMDYOE63CHM7DZZ5KHXAVCNFSM6AAAAABPH6Z5IWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJUHA3TSNBWHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@hatsu38 let me know if this makes sense. |
What kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
Explain the motivation for making this change. What existing problem does the pull request solve?
Try to link to an open issue for more information.
#1289
#1260
Does this PR introduce a breaking change?
If this PR introduces a breaking change, please describe the impact and a migration path for existing applications.
Other information
Updating limits 8 KB->30KB.
FYI: https://app.netlify.com/sites/react-dropzone/deploys/6468abcc0afc9f0008ab0b1a
The following image is a confirmation image that it is displayed in the local language on localhost
