| openapi: 3.0.2 | |
| info: | |
| title: FastAPI | |
| version: 0.1.0 | |
| paths: | |
| /: | |
| post: | |
| summary: Root | |
| operationId: root__post | |
| requestBody: |
| openapi: 3.0.0 | |
| info: | |
| title: asd | |
| version: "123" | |
| paths: | |
| /: | |
| post: | |
| requestBody: | |
| content: | |
| application/json: |
When it comes to usability one of the main key points that should be taken into consideration is knowing the different personas of your product.
I can identify at least 5 different groups that will use swagger-ui within a products lifecycle:
| const MyLogoutPlugin = () => ({ | |
| statePlugins: { | |
| auth: { | |
| wrapActions: { | |
| logout: (internalLogoutAction) => (keys) => { | |
| // here, you can run the logout request. | |
| console.log("Logout from following securities:", keys) | |
| return internalLogoutAction(keys) // don't forget! otherwise, Swagger UI won't logout | |
| } | |
| } |
| import SwaggerUI from "swagger-ui-react" | |
| import React from "react"; | |
| import "swagger-ui-react/swagger-ui.css" | |
| const App = () => | |
| <SwaggerUI | |
| url="https://gist.githubusercontent.com/mathis-m/fcd7022b7f7db2e14112a87ab7c3b637/raw/13bc4f249391f88c1cdde1b51cc2d791e7518d6b/date-picker.yaml" | |
| plugins={[ DateTimeSwaggerPlugin ]} | |
| /> |
| openapi: 3.0.0 | |
| info: | |
| version: "{version}" | |
| title: Sample API with anyOf and oneOf | |
| paths: | |
| /test: | |
| get: | |
| parameters: | |
| - in: query | |
| name: afterDate |
| import React from "react"; | |
| import DatePicker from "react-datepicker"; | |
| import "react-datepicker/dist/react-datepicker.css"; | |
| const JsonSchema_string_date = (props) => { | |
| const dateNumber = Date.parse(props.value); | |
| const date = dateNumber | |
| ? new Date(dateNumber) | |
| : new Date(); |
| type: string | |
| format: date-time |
| type: string | |
| format: date |
| `JsonSchema_string` |
