[Breaking Change] Update RequiredIf Validator to Accept UDF/Closure and Update UDF Validator for Consistency When Handling Null/Empty Values
#78
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.
This change adds additional functionality to the
RequiredIfvalidator. Now, you can pass a UDF/closure to the validator to dynamically evaluate whether the field is required or not. The UDF/closure should returntrueif the field is required andfalseif not.Example:
The
UDFvalidator was also updated for consistency (see ortus-docs/cbvalidation-docs#13) and will treat null/empty values as valid. Developers who want to dynamically determine whether a field should be required will need to switch to usingRequiredIf. This is a BREAKING change and should be reserved for the next major version of CBValidation.