swagger-api / swagger-api/swagger-ui
Deeplinking replaces entire route of the page.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 29k
- Forks
- 9.3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 25
Description
Q&A (please complete the following information)
- OS: [e.g. Windows]
- Browser: [e.g. chrome]
- Version: [e.g. 142.0.7444.0]
- Method of installation: [e.g. npm]
- Swagger-UI version: [e.g. 5.29.3]
- Swagger/OpenAPI version: [e.g. Swagger 3.0]
Content & configuration
I'm integrating swagger-ui-dist in Angular 20, but if I enable deeplinking, it replaces the entire route of the page to "/#/xxx".
How can I prevent this behavior and enable the deeplinking together?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing swagger-ui-dist with deeplinking enabled inside Angular 20 and observe how the browser route changes. Read the deeplinking behavior and Angular routing integration first; done means deeplinking still works without replacing the page's entire route.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100