You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. 🐔
The text was updated successfully, but these errors were encountered:
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.
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.
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. 🐔
The text was updated successfully, but these errors were encountered: