Open abhishek-12355 opened 5 years ago
Great idea. We need to think more about establishing the source of enum in a way that neatly fits into Postman. Something to explore when we go to our next round of work on Environments
I have a similar issue on a simply env var, I would like to define on myself (without swagger) a simple ENUM var, with a list of possible values since they are many.
Any update on this issue?
Thought it was default behavior the first time I used Postman. Quite disappointed when I figured out it was not.
It'd be a great feature ! Would make Postman more easy to use...
Any update on this feature? Must need
Will this feature be implemented? Very needed!
Nearly May 2023 and Postman still has poor OpenAPI support. I mean not being able to provide a selection of parameter enum values?! Any updates on this? This is table-stakes.
@shamasis this doesn't belong in Environments ... it's part of the schema.
Would be great if this issue can be addressed.
If nothing else, being able to define multiple instances of a path variable with different values and let the user use a checkbox to choose which value to use, similar to what can be done within the Query Params section.
Problem I always have to re-type the value of path variable which can be picked from enum. Consider the following rest service GET /api/v1.0/entities/:type where type can be any of ["book", "stationery", "toy", ...]
If I need to fetch book entities, I'll have to type in "book" in the "Path Variables" section. If I need to fetch stationery, I'll have to type in "stationery".
Describe the solution you'd like I think we can display an enumeration through which user can select the value he needs. This should be similar to what we get for example in Content-Type Header
Also it would be simpler to just click on the Path Variable in URL bar and select the appropriate enum. In above API we can click on ":type" which would display the list ( ["book", "stationery", "toy", ...]). User can select the appropriate value from this list.