We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It appears that
<input name="coordinate.northing" ref={register} /> <ErrorMessage errors={errors} name="coordinate.northing" />
does not function properly. Is this known/expected?
I noticed this test
error-message/src/ErrorMessage.test.tsx
Lines 130 to 143 in 9eb1da1
But I don't see the same result.
Maybe this is an issue for the main repo since the errors object sent to this component contains
{ northing: {message: '', type: ''} }
updating the error message to
<ErrorMessage errors={errors} name="northing" as={ErrorMessageTag} />
does work but that is confusing and can lead to non-unique keys.
I messed up. the errors object is coming from my yup resolver schema so once I linked everything up it does work as expected.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It appears that
does not function properly. Is this known/expected?
I noticed this test
error-message/src/ErrorMessage.test.tsx
Lines 130 to 143 in 9eb1da1
But I don't see the same result.
Maybe this is an issue for the main repo since the errors object sent to this component contains
updating the error message to
does work but that is confusing and can lead to non-unique keys.
update
I messed up. the errors object is coming from my yup resolver schema so once I linked everything up it does work as expected.
The text was updated successfully, but these errors were encountered: