[BUG] Incorrect repoUrl for 'AsyncAPI-format' in CLIs tools list
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 75/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- nextjs, react, typescript
- Domain
- content
Research direction
Open config/tools-manual.json and find the AsyncAPI-format entry under the CLIs category; compare its repoUrl with the matching entry in the Converters section. Change the CLI entry to https://github.com/thim81/asyncapi-format, then verify the AsyncAPI Tools page links to that repository when CLIs is selected.
Written by the indexing model from the issue text.
Description
Describe the bug.
In config/tools-manual.json, under the CLIs category, the tool AsyncAPI-format incorrectly links to the converter-go repository (httpsa://github.com/asyncapi/converter-go).
Expected behavior
The repoUrl for AsyncAPI-format in the CLIs section should point to the correct repository, which is https://github.com/thim81/asyncapi-format (as correctly listed in the Converters section).
Screenshots
1]
How to Reproduce
1] Go to the public AsyncAPI Tools page: https://asyncapi.com/tools
2] Filter the list by checking the "CLIs" category.
3] Find the tool card named "AsyncAPI-format".
4] Click on its "GitHub" link (the little GitHub icon).
5]You will be incorrectly redirected to the https://github.com/asyncapi/converter-go repository.
This link should actually go to https://github.com/thim81/asyncapi-format.
🖥️ Device Information [optional]
- Operating System (OS):
- Browser:
- Browser Version:
👀 Have you checked for similar open issues?
- I checked and didn't find similar issue
🏢 Have you read the Contributing Guidelines?
- I have read the Contributing Guidelines
Are you willing to work on this issue ?
Yes I am willing to submit a PR!
- Dominant language
- TypeScript
- Stars
- 717
- Forks
- 1.2k
- Avg merge
- 14h 59m
- Merged PRs (30d)
- 40
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.
More from asyncapi/website
-
📑 docs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
[Improve]:Use top-level` updatedAt` instead of `timelineItems` connection for score calculation Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
area/typescript triaged
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
stale triaged
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
triaged
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in asyncapi/website
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100