feat: Add matches operator to rules
#939
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
kentquirk
force-pushed
the
kent.matches_operator
branch
2 times, most recently
from
a2dc518 to
5c71e7c
Compare
MikeGoldsmith
approved these changes
Dec 11, 2023
kentquirk
force-pushed
the
kent.matches_operator
branch
from
5c71e7c to
93bb3c1
Compare
Closed
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.
Which problem is this PR solving?
matchesoperator to rules which should make some rules easier to write, especially when dealing with URLs or complex string fields.Short description of the changes
matchesoperatorconditionMatchesOperator(to avoid implementing another one)This is part of #822.
This one will need further documentation, but that will be addressed in a separate PR.