Support valid feedback messages. #840
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
src/FormFeedback.js
Outdated
| tag: Tag, | ||
| ...attributes | ||
| } = props; | ||
|
|
||
| const classes = mapToCssModules(classNames( | ||
| className, | ||
| 'invalid-feedback' | ||
| !valid && 'invalid-feedback', |
There was a problem hiding this comment.
make this one line:
valid ? 'valid-feedback' : 'invalid-feedback'
or even something like
${valid ? '' : 'in'}valid-feedback
|
Hi, when would this get updated in npm? |
jlaramie
pushed a commit
to jlaramie/reactstrap
that referenced
this pull request
Mar 9, 2018
This was referenced Mar 20, 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.
Bootstrap supports form-validation success feedback messages: https://getbootstrap.com/docs/4.0/components/forms/
I added the possibility to provide a valid prop to the render method to add the
.feedback-validclass instead of.feedback-invalid. It might be nicer if we would instead explicitly specifyinvalidorvalid={false}but that would break the current behaviour. Any thoughts?