Contributions
Re: I can't see the "add item" button in swagger UI
kawad1 The rendering of `oneOf` in query parameters as you expect is not currently supported in SwaggerUI. Feel free to register an issue at https://github.com/swagger-api/swagger-ui/issues However, based on your use case, you should achieve all that you need by just having the `deviceIds` as an array. - name: deviceIds in: query required: false style: form explode: true schema: type: array items: type: string If you really want to have two separate schemas for a single string and an array of strings, then split into two parameters. - name: deviceId in: query description: "Single device ID" required: false schema: type: string - name: deviceIds in: query description: "Multiple device IDs" required: false style: form explode: true schema: type: array items: type: string Hope this helps.1View0likes0CommentsRe: Authorization Tag For Basic BASE64 Encoding
Hi KF4UYC You can indeed configure an OpenAPI description to mandate BASE64 auth. First, add a `basic` security scheme to the components object components: securitySchemes: basicAuth: type: http scheme: basic Next, add a security section to apply the scheme to all API paths security: - basicAuth: [] Once done, if you you can 'authorize' (enter username / pw) via Swagger UI I've put together a very simple API to showcase at: Simple API with Basic Auth If possible, I'd move onto something more robust that basic auth, but I'm assuming your constrained by the vendor in this case.7Views1like0CommentsRe: Server Variables - can it be refrenced?
tanz No that's not supported by the OpenAPI Specification. You can always request changes athttps://github.com/OAI/OpenAPI-Specification/issues If you have a common pattern in your servers, then perhaps you can approach it slightly differently: servers: - url: 'https://{env}.domain.com/api/{version}' variables: env: description: Environment - staging or production default: staging enum: - staging - production version: description: API version default: v1 enum: - v1 - v26Views0likes0CommentsRe: Consistent HTTP 500 Error When I Click Export API To SwaggerHUB
Hi zx11ninja Are you able to view any information already in SwaggerHub via the SwaggerHub option in the left menu pane of Explore? If your integration with SwaggerHub looks good, the perhaps you could 'export' your space using the Explore.CLI (https://www.nuget.org/packages/Explore.Cli) and attach it here?2Views0likes0CommentsRe: nested tags | sub-groups | sub-tags
Hi MuriloFsDev_29 Nested tags are not currently supported by SwaggerUI and/or by the OpenAPI spec. There are open issue/feature requests however: OpenAPI:https://github.com/OAI/OpenAPI-Specification/issues/1367 SwaggerUI:https://github.com/swagger-api/swagger-ui/issues/5969 In the interim, you could perhaps employ a different category and tagging strategy within the constraints to emulate nested/grouped tags. For example, tags `category1/tagA`, `category1/tagB`, `category1.tagA` or similar. Hope this helps.28Views0likes0CommentsExplore What's New - Episode 7
📺 Episode 7 of 𝗪𝗵𝗮𝘁'𝘀 𝗡𝗲𝘄 𝗶𝗻 𝗘𝘅𝗽𝗹𝗼𝗿𝗲 is out showcasing the new 𝗦𝗵𝗮𝗿𝗲 𝗦𝗽𝗮𝗰𝗲𝘀 features across the UI and CLI of #SwaggerHubExplore. Topics: 💻 Sharing spaces via the UI 💁 Why we added the collaboration feature 🙇🏻 Exporting/Importing spaces via the CLI 💡 Look ahead to 2024 features for the SmartBear API Exploration offering12Views0likes0Comments