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.
Based on this issue #42, I propose this fix.
I've added some if statements to look for if
self.config.classTo
is the same asself.config.errorTextParent
.The main focus is on these lines:
The codes above find
errorClassElement
based on the values fromself.config.classTo
andself.config.errorTextParent
. If they have the same values, thenerrorClassElement
will take the element fromclassTo
. If not, thenerrorClassElement
will take the element fromerrorTextParent
.Some of these changes are credited from #43 that add or remove valid and invalid classes from input field.
Here, I've created a Bootstrap Form to test out my changes.
https://ryumada.github.io/Pristine-test-bootstrap/