Permalinks don’t work: with tags, and `docExpansion: 'none'`, for operations that don’t have an explicit `operationId`.
See original GitHub issueWhen we’re setting docExpansion: 'none'
in configuration, then giving someone a permalink to a particular endpoint inside a tag, and them clicking it doesn’t do anything for them.
After the page opens for them, all endpoints are still not expanded, as if there was no /#/permalink/part
in the URL.
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
How to Fix WordPress Permalinks Not Working - ThemeIsle
Just open your WordPress dashboard and go to Settings → Permalinks. Make sure the permalink structure of your choice is selected. If it's ......
Read more >Does Swagger UI have permalinks for paths? - Stack Overflow
Yes, Swagger UI has permalinks for operations and tags. To get a permalink, expand an operation or tag and copy the URL in...
Read more >WordPress Permalinks Not Working: How to Fix Broken Links
Is your website getting the "404 Page Not Found" error? Here's our guide on how to fix broken permalinks in WordPress.
Read more >WordPress Permalinks Not Working: Effective Methods to ...
So without further ado, let's get started. Table Of Contents. What Triggers WordPress Permalinks Issues? Installing New Plugins; Updates; Migrating WordPress to ...
Read more >How to configure Nginx for Wordpress permalinks - nixCraft
How can I configure Nginx for WordPress permalinks using virtual hosting? A permalink is nothing but the web address used to link to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The
_
problem is different, I think (and covered in #4895) - that is rooted in my ill-conceived implementation that escapes whitespace in deep link hashes with_
instead of the now-obvious%20
.my_operation_id
, when parsed back into Swagger UI from the hash, becomesmy operation id
, which fails to match up with anything that Swagger UI knows about.@michalrus, sure, shoot me an email and I’ll take a look!