-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(plugins): Request-Transformer rename behavior #13358
Conversation
e3337af
to
c8d553b
Compare
c8d553b
to
ed2e35c
Compare
ed2e35c
to
10582fa
Compare
700ace5
to
96960d6
Compare
96960d6
to
399042e
Compare
82003dd
to
8c8cd86
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not really sure if it is designed on purpose, what would most people expect in this scenario? (Because it seems like the behavior has been existing for a long time, and this is the first time we received a question about it)
8c8cd86
to
c407013
Compare
How about also adding a test in which oldname and newname are exactly the same? |
0733c1a
to
3a56e5e
Compare
Successfully created cherry-pick PR for |
Summary
This plugin removes the target parameter when renaming from the same parameter.
Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
Fix KAG-4915
Also see #9442