-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Environment variables in collections #851
Environment variables in collections #851
Conversation
Hey @sboulema, TravisBuddy Request Identifier: f8f33770-9094-11ea-931a-79bfa81bc315 |
Hey @sboulema, TravisBuddy Request Identifier: 60ed2310-9101-11ea-ba10-7b1b65697aa0 |
Hey @sboulema, TravisBuddy Request Identifier: 16e79940-9141-11ea-ba10-7b1b65697aa0 |
Hi @sboulema , thanks for the quick PR, I like the simplicity of the implementation. But there's an issue. While restoring a request from collections, the To reproduce: goto deploy preview: https://deploy-preview-851--postwoman.netlify.app/ 1: create and save a request with env variables to collection.2: click saved request from collection to restore it.As you can notice, when we restore the request - the I think we can store the env variable as it is (without converting to env values) while saving to collections. What do you say about that? I wanna hear from you. |
Hey @sboulema, TravisBuddy Request Identifier: d86eaa30-916f-11ea-ba10-7b1b65697aa0 |
Thanks for the very clear reproducing steps! Should be ok now :) And yes I completely agree, it should always save non-replaced version of the uri and only use replaced version when doing the actual request and showing in the history list. |
Fixes saving a request when using environment variables.
url and path variables get overwritten with replaced values, so before saving we reconstruct them using the original uri variable.
This PR intends to fix #642.