Skip to content

chore: update tools.json #4354

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.

Sign up for GitHub

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

Merged
asyncapi-bot merged 1 commit into from
Aug 25, 2025
Merged

chore: update tools.json #4354

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions config/all-tags.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -178,12 +178,12 @@
"borderColor": "border-[#B9012b]"
},
{
"name": "TypeScript",
"name": "Socket.IO",
"color": "bg-[#61d0f2]",
"borderColor": "border-[#40ccf7]"
},
{
"name": "Socket.IO",
"name": "TypeScript",
"color": "bg-[#61d0f2]",
"borderColor": "border-[#40ccf7]"
},
Comment on lines +181 to 189
Copy link
Contributor

@coderabbitai coderabbitai bot Aug 25, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Swapped "Socket.IO" and "TypeScript" technology tags — verify downstream exact-name matches

Tools rely on exact string matches. Please double-check that every reference in config/tools.json and config/tools-automated.json uses "Socket.IO" and "TypeScript" with this exact casing and punctuation. I see mixed casing elsewhere (e.g., "React js", "Typescript", "NestJS") that will break filtering.

Run this quick consistency check:

🏁 Script executed:

#!/bin/bash
# Known tags from all-tags.json
langs=$(jq -r '.languages[].name' config/all-tags.json | sort -u)
techs=$(jq -r '.technologies[].name' config/all-tags.json | sort -u)

echo "=== Potentially mismatched tokens in tools-automated.json ==="
# Find technology/language tokens not present in all-tags.json
jq -r '
  .. | objects | select(has("filters")) |
  . as $t |
  ([$t.filters.language] | flatten | map(tostring)) as $langs |
  ($t.filters.technology // [] | map(tostring)) as $techs |
  ([$t.title, ($langs[]? // empty), ($techs[]? // empty)] | @tsv)
' config/tools-automated.json |
awk -F'\t' '{print $2"\n"$3}' | sed '/^$/d' | sort -u > /tmp/seen.txt

echo "Unknown languages:"
comm -23 <(grep -Fxf /tmp/seen.txt <(echo "$langs") || true) <(echo "$langs") | sed 's/^/  - /' || true

echo "Unknown technologies:"
comm -23 <(grep -Fxf /tmp/seen.txt <(echo "$techs") || true) <(echo "$techs") | sed 's/^/  - /' || true

echo "Suspicious casing:"
rg -n 'React js|Typescript|NestJS|github-actions' config/tools-automated.json || true

Length of output: 2831

Ensure exact tag names for filters in config

I ran a consistency check between config/all-tags.json and the downstream config files and found several mismatches in config/tools-automated.json that will break filtering:

  • config/tools-automated.json (line 147):
    "language": "Typescript" → should be "TypeScript"
  • config/tools-automated.json (line 150):
    "NestJS" → should be "Nest Js"
  • config/tools-automated.json (line 379):
    "React js" → should be "React JS"
  • config/tools-automated.json (line 502):
    "github-actions" → should match the canonical tag (e.g. "GitHub Actions")

Please update these entries to exactly match the name values (including casing and punctuation) defined in config/all-tags.json. Also verify config/tools.json for any similar mismatches.

🤖 Prompt for AI Agents 
In config/all-tags.json around lines 181-189 and config/tools-automated.json at
the referenced lines, several tag values must exactly match the canonical names:
update config/tools-automated.json line 147 from "Typescript" to "TypeScript",
line 150 from "NestJS" to "Nest Js", line 379 from "React js" to "React JS", and
line 502 from "github-actions" to "GitHub Actions" (match punctuation and casing
from all-tags.json); after making those exact replacements, scan
config/tools.json for any other tag mismatches and correct them to the canonical
names in config/all-tags.json.

Expand Down
Loading
Loading