You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
###Bug-Description
There is a broken link in the tools section of the AsyncAPI website. When clicking on the link, it should direct the user to the AsyncAPI server API section but it currently does not.
Screen.Recording.2025-03-05.172818.mp4
Expected behavior
on clicking it should direct towards the asyncapi server api section
Screenshots
How to Reproduce
1.just go to the tools section
2.click on the visit website under asyncapi server api .
Fixesasyncapi#3797
Remove the `View Website` button from the `AsyncAPI Server API` card in the `components/tools/ToolsCard.tsx` file.
* Update the condition to check for `toolData.links.repoUrl` or `toolData.links.docsUrl` instead of `toolData.links.repoUrl` or `toolData.links.websiteUrl` or `toolData.links.docsUrl`.
* Remove the code block that renders the `View Website` button for `toolData.links.websiteUrl`.
Fixesasyncapi#3797
Fix the broken link in the tools section of the AsyncAPI website.
* **config/tools-automated.json**
- Update the "websiteUrl" link for "AsyncAPI Server API" to remove the broken link.
* **config/tools.json**
- Remove the "websiteUrl" link for "AsyncAPI Server API" to ensure proper navigation.
###Bug-Description
There is a broken link in the tools section of the AsyncAPI website. When clicking on the link, it should direct the user to the AsyncAPI server API section but it currently does not.
Screen.Recording.2025-03-05.172818.mp4
Expected behavior
on clicking it should direct towards the asyncapi server api section
Screenshots
How to Reproduce
1.just go to the tools section
2.click on the visit website under asyncapi server api .
🥦 Browser
Brave
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: