feat: allow validation pattern to be a RegExp or a string [] #1304
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
jjolton-contentful
force-pushed
the
feat/allow-pattern-to-be-regexp-or-string
branch
4 times, most recently
from
eea81d1
to
8100cbe
Compare
jjolton-contentful
force-pushed
the
feat/allow-pattern-to-be-regexp-or-string
branch
from
8100cbe
to
bd436d2
Compare
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.
Summary
regexpandpreventRegexpcurrently only accept a regexp that is represented as apatternstring and itsflags, but it should also be able to accept a RegExp directly, see #1178 for more details.Description
Both
regexpandprohibitRegexpvalidations will now support either the existingpattern/flagsformat or a RegExp directly