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
The action buttons below the request body table ('Fill Example', 'Clear', 'Try') only really make sense in context of the examples tab. If you have the schema tab open and you click the 'Clear' button for example, you don't see the effect of that until you switch back to the examples tab, which can be confusing.
It would be better if these buttons were only visible when the schema tab is selected.
The text was updated successfully, but these errors were encountered:
this is bit more trickier than that. There can be other inputs like Query-Params , Path-Params, multipart form data like this where some section shows input values and some shows schema.
Will you still hide those buttons ?
will it confuse the user why he isn't seeing a TRY button if the default tab is set to schema
I will extended the question to our clients to receive feedback, meanwhile people can also provide there opinion here . I will keep it open for some more time before we make a decision on it
The action buttons below the request body table ('Fill Example', 'Clear', 'Try') only really make sense in context of the examples tab. If you have the schema tab open and you click the 'Clear' button for example, you don't see the effect of that until you switch back to the examples tab, which can be confusing.
It would be better if these buttons were only visible when the schema tab is selected.
The text was updated successfully, but these errors were encountered: