ContributionsMost RecentMost LikesSolutionsRe: 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. Explore 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 offering Re: Domain With SwaggerHub SaaS, this is not possible. Other options: - SwaggerHub on-prem - SwaggerHub Portal - where you can brand your API portal and make your API products available to consumers. You'll also have flexibility over the subdomain, and it's on the backlog to support full customer domains with url rewrites etc. Explore What' New - Bonus Episode #2 Bonus edition ๐ช๐ต๐ฎ๐'๐ ๐ก๐ฒ๐ ๐ถ๐ป ๐๐ ๐ฝ๐น๐ผ๐ฟ๐ฒ๐บis out showcasingtwo new capabilities to the ๐๐ ๐ฝ๐น๐ผ๐ฟ๐ฒ ๐๐ผ๐บ๐บ๐ฎ๐ป๐ฑ ๐๐ถ๐ป๐ฒ ๐จ๐๐ถ๐น๐ถ๐๐ (๐๐๐) ๐๐ The latest version supports additional commands to: โ ๐๐ก๐๐๐๐-๐๐๐๐๐๐ โ making it easy to export, edit, share spaces โ๏ธ โ ๐๐๐๐๐๐-๐๐๐๐๐๐ โ upload edited spaces back into Explore or import spaces stored off in your SCM ๐ https://www.youtube.com/watch?v=8kngmRXmFnI Explore What's New - Episode 6 ๐บ Episode 6 of ๐ช๐ต๐ฎ๐'๐ ๐ก๐ฒ๐ ๐ถ๐ป ๐๐ ๐ฝ๐น๐ผ๐ฟ๐ฒ is outshowcasing the new ๐๐ป๐๐ฒ๐ด๐ฟ๐ฎ๐๐ถ๐ผ๐ป ๐ฒ๐ป๐ต๐ฎ๐ป๐ฐ๐ฒ๐บ๐ฒ๐ป๐๐ ๐๐ถ๐๐ต ๐ฆ๐๐ฎ๐ด๐ด๐ฒ๐ฟ๐๐๐ฏ. Topics: ๐ version switching on an OpenAPI description ๐ป Server endpoint selections ๐ Navigating to the full OpenAPI description from Explore https://www.youtube.com/watch?v=TlH4rm5yGiM Explore What's New - Bonus Episode #1 ๐ขBonus edition ๐ช๐ต๐ฎ๐'๐ ๐ก๐ฒ๐ ๐ถ๐ป ๐๐ ๐ฝ๐น๐ผ๐ฟ๐ฒ ๐บ is out showcasing a little ๐๐ ๐ฝ๐น๐ผ๐ฟ๐ฒ ๐๐ผ๐บ๐บ๐ฎ๐ป๐ฑ ๐๐ถ๐ป๐ฒ ๐จ๐๐ถ๐น๐ถ๐๐ (๐๐๐) ๐which helps importing data intoSwaggerHub Explore. The initial version supports importing API collections fromSwaggerInspector. This is particularly timely as weโre planning to sunset ๐ Swagger Inspector๐ at the end of September ๐ Topics covered: ๐ญScope of the CLI tool ๐ Prerequisites and installation โ Running the CLI to import your collection ๐ Exploring your new spaces in SwaggerHub Explore https://www.youtube.com/watch?v=TeYg6tSht6Y Re: $ref: not being followed Hibobfischer, When specifying the path reference, you have to use JSON Pointer notation to correctly reference the correct part of the file being referenced. Here's an example of how we would do it in SwaggerHub, leveraging SwaggerHub domains to store the individual (or reusable) path item. See API example in SHUB: https://app.swaggerhub.com/apis/frank-kilcommins/Path-References/0.0.1 If your using the open source editor or other tooling and wanting to use multi-file descriptions, you still need to provide the reference to the correct part of the file. I would also recommend keeping each file as a valid OpenAPI file. So, here would be how I would specify the SelectSpeaker path item file: openapi: 3.0.0 info: version: 1.0.0 title: Speakers API Fragment paths: '/speakers/{name}': get: summary: Select a Speaker description: Get a speaker based on their name tags: - speakers parameters: - name: name in: path required: true description: Name of the speaker to be selected. schema: type: string maxLength: 100 minLength: 1 pattern: '^[a-zA-Z-\s]+$' responses: 200: description: Success content: application/json: schema: type: object properties: status: type: string maxLength: 20 minLength: 1 example: success additionalProperties: false 406: description: Not Acceptable 429: description: Too Many Requests And then have the main OpenAPI description reference as follows: openapi: 3.0.0 info: version: 1.0.0 title: Speakers API Fragment paths: '/speakers/{name}': $ref: "https://raw.githubusercontent.com/frankkilcommins/OAS-Examples/main/OAS3_0/speakers-api-fragment.yaml#/paths/~1speakers~1{name}" Above shows an absolute URL but you can reference relative files on the same host. The most important part is how I get to the pathitem in the file `#/paths/~speakers~1{name}`. Seehttps://swagger.io/docs/specification/using-ref/for me info. Hope this helps. Cheers, Frank Re: Validating inline-examples against inline-schemas HiBUITP03, We have an open issue for this registered on the GitHub repo for Swagger Editor. Seehttps://github.com/swagger-api/swagger-editor/issues/4389 Perhaps you could add your support and wishes for that ability in the issue? Cheers, Frank Re: $ref: not being followed Hibobfischer, Could you share some examples of the referenced files (e.g. reloadData.yaml and selectSpeaker.yaml)? Cheers, Frank Re: Render Html pages coming as response of get API Himalik_nisha, It sounds like you're trying to implement an OAuth 2.0 or OpenID Connect server. The implementation of such is outside of the scope of Swagger tooling. If you have such a server in place (or even better if you use a battle testing identity provider), then you can leverage it to protect your APIs using OpenAPI spec. See the OAuth 2.0 docs for information on how to configure the security schemes. Once an API description (i.e. an OpenAPI definition) has been setup correctly with the relevant security schemes and the path items require security, then the `Authorize` button in SwaggerUI will render the appropriate form for you to enter the appropriate data and communicate with the configured OAuth provider. You can also set the OAuth configuration before user interaction, you can also refer to here Hope this helps. Cheers, Frank