This is a weird one but bear with me.
The following will work as expected:
- Load the root examples URL: https://redocusaurus.vercel.app/
- Navigate to
Examples -> Using Single YAML
- Click e.g.
General -> Pet -> Find pet by ID
Outcome: The anchor is loaded, and the browser URL is updated correctly to: ...#tag/pet/operation/getPetById
However if you instead access the example directly (or refresh the page once you're there) it will cause a bug in the navigation:
- Load the example directly: https://redocusaurus.vercel.app/examples/using-single-yaml
- Click e.g.
General -> Pet -> Find pet by ID
Outcome: The anchor is loaded BUT the browser URL is now updated to ...#tag/pet/operation/updatePet NOT ...getPetById
In fact regardless of which link is clicked, the browser URL will be set to the previous entry in the list to the one you clicked.
And indeed this behaviour is present in deployments of the plugin, not just the examples. Which is problematic because people often bookmark this openAPI-generated section rather than the top level of the docs because it has the most useful content.
This is a weird one but bear with me.
The following will work as expected:
Examples -> Using Single YAMLGeneral -> Pet -> Find pet by IDOutcome: The anchor is loaded, and the browser URL is updated correctly to:
...#tag/pet/operation/getPetByIdHowever if you instead access the example directly (or refresh the page once you're there) it will cause a bug in the navigation:
General -> Pet -> Find pet by IDOutcome: The anchor is loaded BUT the browser URL is now updated to
...#tag/pet/operation/updatePetNOT...getPetByIdIn fact regardless of which link is clicked, the browser URL will be set to the previous entry in the list to the one you clicked.
And indeed this behaviour is present in deployments of the plugin, not just the examples. Which is problematic because people often bookmark this openAPI-generated section rather than the top level of the docs because it has the most useful content.