adding http_matcher.feature v3 compatibility test #751
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
valkolovos
force-pushed
the
http_matcher_compatibility_test
branch
from
7976afa to
18a65e1
Compare
JP-Ellis
force-pushed
the
http_matcher_compatibility_test
branch
from
18a65e1 to
c6f0358
Compare
JP-Ellis
approved these changes
Aug 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Adding a v3 compatibility test for the http_matching feature. This seemed like an easy add since there were no code changes outside of testing code required.
🔥 Motivation
Since I want to work on V3 matchers, my motivation was to learn a little more about how matchers work and move the overall V3 compatibility forward.