Export FieldErrors component #371
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dferber90
force-pushed
the
df-export-field-errors
branch
from
55e8288 to
0b3e188
Compare
montezume
approved these changes
Dec 27, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
FieldErrorscomponentFieldErrors.errorTypesconstants which aim to make code of consumers easier to follow by avoiding "magic" keys likemissingin the errors object by showing the constants instead (non-breaking change)react-testing-librarytests for the public APIREADMEI didn't add a story as this component doesn't have any visuals itself (apart from rendering
ErrorMessagewhich is already tested separately).Closes #246