This repository was archived by the owner on Aug 15, 2021. It is now read-only.
forceValidation and forceValidationIfPopulated #161
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
…d repo link for temporarily forked repo.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The main reason for this fork was to add logic to show validation styling for fields that are pre-populated before rendering. Since the form fields are pristine in this case, they do not show validation formatting and will not do so unless the field is changed. I added a new forceValidationIfPopulated option to force any field that is populated to always show validation styling. This is different than the forceValidation option in that I only want pre-populated fields to be styled on page load.
I also noticed that the forceValidation option was effectively disabled because the option was hardcoded to false instead of being parsed. I wasn't sure whether this was intentional because the functionality is not yet ready for release, or accidental. Basic testing suggested the functionality worked, so I added the proper parsing.