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

URL Segment Params #2

Closed
hilkins opened this issue Sep 8, 2015 · 2 comments
Closed

URL Segment Params #2

hilkins opened this issue Sep 8, 2015 · 2 comments

Comments

@hilkins
Copy link

hilkins commented Sep 8, 2015

It could be nice to have a way to generate URL segment variables instead of global variables. It would be useful when you use common global variables between different collections but want some variables to be unique to some endpoints.

URL segment variables are defined using semi-colon {{host}}/endpoint/:url_var/:another_url_var.
I saw it referenced in that issue. 🐔

@ramnes ramnes modified the milestones: improvement, confirmed Sep 8, 2015
@ramnes ramnes self-assigned this Sep 8, 2015
@ramnes ramnes removed this from the confirmed milestone Sep 8, 2015
@ramnes
Copy link
Collaborator

ramnes commented Oct 14, 2015

Yeah, we could make an option that force all the variables to be segment variables. But I think we should also find a way to differentiate which variable is supposed to be a global or a segment parameter. I'm not sure it's very useful to have only one type of variables.

@ramnes
Copy link
Collaborator

ramnes commented Apr 20, 2016

I don't think it's a useful feature, in comparison to the complexity it would add. I'll close this for now, but I (or someone else) will reopen it if there's a real need.

@ramnes ramnes removed the confirmed label Apr 20, 2016
@ramnes ramnes closed this as completed Apr 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants