API Endpoint operation headers disappeared in latest version

[neptunecentury]

Hi, we have been using the CDN with version 9.3.4 for some time, and the side navigation operation headers were showing before. After this recent update in 9.3.5, the navigation tags are missing.

I have manually downloaded 9.3.4 and removed CDN for now until the issue is resolved. Is there anything on my end I need to update to get this working again?

Thanks

[mrin9]

can you provide me with a small sample spec where i can reproduce this ?

The example which uses RapiDoc 9.3.5 works fine

[douglasg14b]

We're also seeing the same thing on all of our Rapidoc sites

[neptunecentury]

Actually, the demo page for Azure AD is broken too.
You can see it here:
https://rapidocweb.com/examples/api-demo.html
Select AzureAD from options on the right and you will see the headers missing

[mrin9]

it is showing fine on my system Macbook (on chrome and safari)

[neptunecentury]

it is showing fine on my system Macbook (on chrome and safari)

The header in your screenshot is missing. Circled red

[neptunecentury]

The gitlab example is working

[mrin9]

okay got it, lemme check

[mrin9]

@neptunecentury is your sepc swagger: "2.0" ?

[neptunecentury]

Well, we generate swagger 2.0, but use an API to convert it to OpenAPI v3 using the swagger converter here https://converter.swagger.io/api/convert

It generates OpenAPI 3 spec

{"openapi":"3.0.1","info":{"title":"API Reference","description":"## Status Codes a...

[douglasg14b]

We generate 3.0 directly, if that's relevant.

[mrin9]

Is now fixed in release 9.3.6

It was introduced due to a new vendor-extention x-displayName that was added which allows you to provide more descriptive definitions for the tags. like shown below

paths:
  /path:
    get:
      summary: Endpoint
      tags:
        - xyz-id
tags:
  - name: xyz-id
    x-displayName: Custom Tag Name
    description: Custom Tag Description

Refer to https://github.com/rapi-doc/RapiDoc/blob/master/docs/specs/tag-displayname.yaml for its usage

Thanks for pointing out the issue !!!