chore: re-design nginxVars to exprs #306
Merged
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.
Please answer these questions before submitting a pull request
Why submit this pull request?
Bugfix
New feature provided
Improve performance
Backport patches
Related issues
Bugfix
Description
How to fix?
New feature or improvement
This PR renames the
nginxVars
field inApisixRoute
toexprs
, which is more expressive, also, thesubject
inexprs
is re-designed to be an object which contains thescope
andname
field.The
scope
field specifies where to find the subject, it can be:Header
- HTTP request headersCookie
- CookieQuery
- Query stringPath
- URI PathThe
name
field specifies the subject name, which can be empty whenscope
isPath
.Backport patches
Why need to backport?
Source branch
Related commits and pull requests
Target branch