Skip to content
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

[Field] Is forceShow prop necessary? #1200

Open
vladmoroz opened this issue Dec 20, 2024 · 1 comment
Open

[Field] Is forceShow prop necessary? #1200

vladmoroz opened this issue Dec 20, 2024 · 1 comment

Comments

@vladmoroz
Copy link
Contributor

iirc we've discussed that having the forceShow prop can be avoided altogether by just rendering the field error yourself:

{myCondition && <Field.Error>My special error</Field.Error>}
@atomiks
Copy link
Contributor

atomiks commented Dec 21, 2024

<Field.Error> can be specified as a children-less component by default, as it gets automatically populated with error messages. When you use match="{something}", that's when custom children become useful as you can render messages different from the browser's defaults

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants