bvieira080
October 4, 2023, 2:38pm
1
I would like to suggest the feature of ‘Ability to set code snippet always’ as it would be valuable for troubleshooting to clearly identify which variables are being resolved during test execution
Hey @bvieira080
In terms of feature requests, this isn’t the best place to raise them. Messages tend to get lost in amongst other topics
Could I ask that you raised the feature request here , please.
Hey @bvieira080
This feature request seems to be the one that you’d like to see in the product.
opened 11:45PM - 29 Dec 22 UTC
feature
product/runtime
### Is there an existing issue for this?
- [X] I have searched the tracker for … existing similar issues and I know that duplicates will be closed
### Describe the Issue
Variable tooltips show as expected in URLs and other data entry fields (such as auth fields), but do not display when referenced as part of the request body.
I started this as a forum question here: https://community.postman.com/t/tooltip-for-variables-in-post-body/42444 and it was suggested I open a feature request. But when I search previous GitHub issues, I found https://github.com/postmanlabs/postman-app-support/issues/1518 from 2015 where the OP specifically asked for this same feature
> It would be great to have a tooltip if you hover over an environment variable either in the URL or in the request body so you can see the actual value that is going to be used in the current environment.
And PM seemingly honored the request in 2017. But while the tooltip works as shown in the post screenshots, it doesn't really address the request body issue from the OP.
My forum post was closed so I couldn't ask for guidance about opening the issue as feature request vs. defect, but chose the latter since this was apparently the intent of issue /#1518 and subsequent implementation. Maybe it originally worked but broke somehow?
Rationale for this support is same as /#1518 OP - Useful to be able to see variable values being used in all places, esp. as they can very between environments.
### Steps To Reproduce
1. Create a collection or environment variable
2. Crate a new request
3. Reference the variable in the request URL and also in the request body (mine was JSON, just fwiw)
4. Mouse over variable the reference in the URL and tooltip for variable value and details displayed
5. Mouse over the variable reference in the request body and no tooltip or details are displayed
### Screenshots or Videos
See screenshot in https://community.postman.com/t/tooltip-for-variables-in-post-body/42444
### Operating System
macOS
### Postman Version
10.6.7
### Postman Platform
Postman App
### User Account Type
Signed In User
### Additional Context?
Also reproduces in Postman Web
So you closed an active topic again, because you really don’t want people to express themselves,
I’m pretty sure that’s your own definition of “being professional”
It is nothing to be ashamed in this sick work to run for money but it is something else to hide it.
The scratchpad and the logged in version are almost the same (if not the same) app and should work in a very near way (if designed well).
I can believe it is a little work to adapt one flow on the other but you could also have freeze the scratchpad in working state without alter the other branch of your app and continue to enhance it.
Both way, I think you’re lying on your blog, if you want to be professional then start admitting it
The topic was closed because you were posting several unrelated opinion based messages and forcing it to become off topic.
Hi,
In the context of the recent Scratchpad changes, at my company we are keen to look at options that allow us to use Collections but not necessarily have them saved on Postman cloud. One of the options we were thinking on was to save the Collections to Git / Bitbucket.
My question is - Even with git integration for Collections, will Postman still keep a copy of the collection on Postman cloud?
As that looked like it was going to continue to happen, I closed the topic to prevent this.
Closing this as the original topic has been addressed. A feature request for the same issue has been created and this request can be tracked over on Github.
