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
Voting for option to opt-in showing summary or keys or both.
Maybe is ugly for default usage but for specific use cases it is really helpful.
Here is an example
in: queryname: idschema:
type: integerformat: int32minimum: 10000examples:
empty: ## just an empty value ## fixes auto filling examplevalue:
demo-1:
value: 10101canceled-order:
value: 10102order-with-discount:
value: 10103order-with-discount-2:
value: 10104summary: there are multiple discount appliedx-examples-summary-show: titlex-examples-key-show: true
Showing 10101 | 10102 | 10103 | 10104 to user is not helpful.
But showing demo-1 | canceled-order | order-with-discount | order-with-discount is useful and clear what that example will show.
Also, if you could find some place to display summary after user clicks on one example - that would be great.
x-examples-key-show: truex-examples-summary-show: selected # when seelcted only# orx-examples-summary-show: title # show on hover (this should be default: true)
Voting for option to opt-in showing summary or keys or both.
Maybe is ugly for default usage but for specific use cases it is really helpful.
Here is an example
Showing
10101 | 10102 | 10103 | 10104
to user is not helpful.But showing
demo-1 | canceled-order | order-with-discount | order-with-discount
is useful and clear what that example will show.Also, if you could find some place to display
summary
after user clicks on one example - that would be great.Example - swagger
Also there is similar request
The text was updated successfully, but these errors were encountered: