Display {{variable}} value in History / Display request url in app

[duepayer]

It would be great if there was an option to display the {{variable}} value in the History url field. For example, if the request was sent with {{host}}/version/item/info.json, the History section would display "http://prod.host.com/version/item/info.json". This would be helpful for debugging purposes as it is impossible to know what environment the request was set to at the time of execution without it. After reading through past issues I noticed that this was the original functionality but was changed to only display the {{variable}} in the url field - #73. I'm still not sure what the use case is for only seeing the variable but it would be really helpful if we had the option to view the full request url somewhere in the app.

[a85]

I thought about it a lot too. The request with the variable gives the exact representation of the request which is loaded in the editor. Users would then be aware of selecting the appropriate environment. I think it might be more appropriate to save the active environment when the request is sent and show a notification in the UI if that environment is not set.

[KJanik]

From a QA perspective, this would be incredibly useful. I heavily use {{variables}} in my requests due to switching between multiple environments. When something fails, I just grab a screenshot. It would be great if there was a small "expanded" line below the {{variable}} line so the developers can exactly see the request I made without needing my collection and environment. I included a (poor) mockup to clarify the suggestion.

Thank you for the consideration.

[a85]

@KJanik You can click the preview request to see exactly what's sent to the server. This would convert all variables to corresponding values.

[jimpudar]

I still don't think we have a good solution to this issue. I have a request which uses dynamic variables (e.g. {{$randomInt}}) and as far as I can tell there is no way for me to tell what random int got sent with a particular request by observing the history.

Furthermore, the current concept of environments have both initial and current values, suggesting that variables may have different values now than they did when the request was made.

If I click the "Code" button and view the request as cURL or Python, I can see that the dynamic variable is replaced by the current version of that variable, not the value that was actually sent.

Hopefully I'm missing something here?