Skip to content
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

Handling Query Params #11

Open
alexlafroscia opened this issue Aug 25, 2015 · 2 comments
Open

Handling Query Params #11

alexlafroscia opened this issue Aug 25, 2015 · 2 comments

Comments

@alexlafroscia
Copy link
Collaborator

Is there currently any way to handle the need to convert a dynamic segment to a query param when doing the redirect? If not, is this something you might be interested in a PR for? If we can decide on the user-facing API for that, I would be interested in putting together a PR for it.

@thoov
Copy link
Owner

thoov commented Aug 25, 2015

Currently there is not a way to do this but that would be an awesome PR! Let me know if you need any help or to bounce any ideas off of.

@alexlafroscia
Copy link
Collaborator Author

I needed to implement something today, so I was looking into it a bit. It seems like it would be pretty easy to translate the exact query params from one route to another, but what might it look like if you needed to change them? We'd need to go beyond simple key: value, but probably open the value up to being an object or something like that...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants