feat: add negate_match feature for propagate regular expressions #87
+22
−9
Conversation
This file contains hidden or 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
SkArchon
force-pushed
the
milinda/eng-7207-support-template-expression-in-header-request-forwarding
branch
from
2600463 to
7c4a4d1
Compare
SkArchon
force-pushed
the
milinda/eng-7207-support-template-expression-in-header-request-forwarding
branch
from
7c4a4d1 to
4186ac6
Compare
SkArchon
changed the title
alepane21
requested changes
May 29, 2025
alepane21
approved these changes
May 29, 2025
|
Thanks |
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.
Motivation
We introduce
negate_matchas a new attribute because go does not support negative lookahead regexes and we want to allow users a workaround to simulate this.