-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Add ability to transform query params on redirector services #3118
Comments
So I was originally only thinking about this in the context of a redirect being able to transform a route param to a query param, but as I've started working on this I realized that there may be a scenario when one would want to rename a query param (as part of a redirect, or even just in general) My current thinking/assumption: #3042 added functionality that allows a service to specify query params via a Joi schema, and therefore renaming of a query param ( Accordingly, I'm not currently planning on adding functionality to the redirector for renaming/transforming one query param to another query param. Please let me know if I've got anything wrong there and/or if anyone feels differently |
Redirecting is a bit different from renaming. Redirecting is more cache-friendly. It's nice for the user, and I think less confusing, to canonicalize the query params as we're rewriting the URL, particularly the badge-specific query params. Though that probably is relatively low priority. As I think about it, the more important case of redirecting the query params would be in the context of an existing service (i.e. where the route is the same, but the query params are rewritten). So that feels like a different project entirely. |
So agreement that it's sufficient for the redirector I.e. redirect: |
Yep! |
Dialog in #3074, in particular #3074 (comment)
Use case/benefit is being able to simplify route patterns by moving certain optional params (for example tokens, urls, etc.) from route to query params
The text was updated successfully, but these errors were encountered: