Add warning state to localized inputs e.g. <LocalizedTextInput>
See original GitHub issueSummary
All simple inputs support both error and warning states. In recent discussions with design we learned that we also need warning states on localised inputs. Just like their error messages.
Description
Given an e.g. <LocalizedTextInput> is used I want to pass warnings
just like errors
which are rendered under the respective localisation in orange tone.
Alterantives
Showing the warning above the input itself. This however does not work when e.g. wanting to recommend (not enforce through errors) that a single localisation is unique across a set of entities.
Visuals
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
<input>: The Input (Form Input) element - HTML
A field for editing an email address. Looks like a text input, but has validation parameters and relevant keyboard in supporting browsers and ......
Read more >LocalizedStringKey | Apple Developer Documentation
Represents the contents of a string literal with interpolations while it's being built, for use in creating a localized string key.
Read more >Localized Input - Clay
A text input variation used in fields that can be translated into multiple languages. Use it when you want to enable the users...
Read more >Localization on mobile devices
Use these steps to add translations for your mobile device that are not already translated by your mobile device's native translation settings.
Read more >Localized Form Validation | Phrase
When we add the need to localize our forms (and our validation errors) to the ... a template for a form field like...
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 FreeTop 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
Top GitHub Comments
Yes, I think that’s a concrete example to the general UX approach I think. If form won’t have errors so it can be saved but we’re warnings/giving a recommendation towards something.
No need yet. You can if you want to but it’s not an urgent request.