-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Deep linking does not work for operations with tags containing spaces #4120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Also bumped into this. Would be great if it was fixed. |
If I change this line into let isShownKey = ["operations", tag.replace(/ /g, "_"), operationId] it starts working. But I think it isn't meant to be solved that way. Too bad I don't have the spare time to properly get accustomed with the source code to do a proper merge request. |
This is causing issues on the CURL the issue was reported on #4263 |
Is there any progress on the pull request? Or any update if this will be fixed soon? |
Same question here.any target date to resolve this? |
#4953 should solve this 😄 thanks for the report! |
Demonstration API definition
Change the tag "pet" in the sample petstore.json to be "pet v1" or any other value containing a space.
Expected Behavior
Example operation: POST /pet with the tag "pet v1"
The link http://localhost:3200/#/pet_v1/addPet (replace localhost with whatever the host is) should result in the UI scrolling to the operation POST /pet.
Current Behavior
The UI does not scroll to the linked operation when the operation tag contains a space. In this example, the id of the html element for the operation POST /pet is "operations-pet v1-addPet".
Possible Solution
In this example, the element id of the operation POST /pet is "operations-pet v1-addPet". The space in this id breaks linking. The element id in this example should probably instead be "operations-pet_v1-addPet".
Context
Users expect that the linked operation should be scrolled to.
The text was updated successfully, but these errors were encountered: