API Console feature
Implement API Console functionality. Each method in ReDoc will have a button: “Try this method” which will open interactive console modal window. ### There is the list of key features that should be implemented in the first version: - Ability to send GET, POST, PUT, DELETE, UPDATE requests - Ability to input/use/save authorization credentials - Show UI for easy entering parameters for path, headers, query and body (payload) parameters - UI should show selectbox for enums, checkboxes for boolean, text input for other simple types - Request should be validated before send according to OpenAPI spec - Support different environments (e.g. sandbox, dev, testing, etc) through OpenAPI vendor extension (each env will have unique base url and description) + ability to set default env specially for API-console - For most parts response will be shown “as is”. JSON response will be only prettified (with possibility of collapsing). The other responses will be represented as strings. - Show response headers that are documented in swagger. HTTP response headers that are not documented will be hidden under “Show undocumented response headers” button
Posted by RomanHotsiy on May 31, 2016, 9:38 AM
Tags
Related issues
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
API Console feature
Implement API Console functionality. Each method in ReDoc will have a button: “Try this method” which will open interactive console modal window. ### There is the list of key features that should be implemented in the first version: - Ability to send GET, POST, PUT, DELETE, UPDATE requests - Ability to input/use/save authorization credentials - Show UI for easy entering parameters for path, headers, query and body (payload) parameters - UI should show selectbox for enums, checkboxes for boolean, text input for other simple types - Request should be validated before send according to OpenAPI spec - Support different environments (e.g. sandbox, dev, testing, etc) through OpenAPI vendor extension (each env will have unique base url and description) + ability to set default env specially for API-console - For most parts response will be shown “as is”. JSON response will be only prettified (with possibility of collapsing). The other responses will be represented as strings. - Show response headers that are documented in swagger. HTTP response headers that are not documented will be hidden under “Show undocumented response headers” button
Comments (0)
No comments yet. Start the discussion.