asyncapi
Server anchor navigation url parameter problem
Related pull request: #1098 Related issue: #1097
Description
I'm generating my documentation dynamically based on a URL parameter. The URL looks like: http://localhost/async_docs?test=1234
Now I click on a server link in the "Available only on servers" section.
Expected result
Navigating to /async_docs?test=1234#server-broker
Actual result
Navigating to /async_docs#server-broker
> The URL parameters are ignored
Steps to reproduce
See the description
Troubleshooting
Looked at the source code and found #1098
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Greetings @Fabi-02 and mentors, can you please assign this issue to me
@Fabi-02 @afraazali001 In this organization, issues are not assigned as it can be blocking. Feel free to raise a PR directly when you have a fix ready 😃.
@afraazali001 @itsmanasdash, still interested in raising a PR for this issue?
This issue has been automatically marked as stale because it has not had recent activity :sleeping:
It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.
There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.
Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.
Thank you for your patience :heart:
Hi, I’d like to work on this issue as part of my contributions to the AsyncAPI organization.
