chore(raycast): rename extension off the "Axle" trademark#35
Merged
Conversation
npm was the only distribution channel the dashboard could see. The VS Code extension (asafamos.axle-a11y) had 19 installs + a 5★ rating that were invisible — discovered only by digging through old publish emails. - Fetch the public VS Marketplace gallery API server-side (extensionquery, flags 914) for install/download/rating counts. Resilient: any failure yields zeros, never breaks the page. - New "VS Code Marketplace" section in /admin, alongside npm. - Drive-by: fix a pre-existing react-hooks/set-state-in-effect lint error on the token-load effect (documented disable — the effect read is intentional for SSR hydration-safety). Verified: tsc + eslint clean; the fetch/parse path returns live data (19 installs / 59 downloads / 5.0★). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The WordPress.org review flagged "Axle" as colliding with the existing "Axle AI" project; we renamed the WP plugin to "AsafAmos Accessibility Scanner". The Raycast extension carried the same "Axle" name, so apply the same rename before resubmitting (the raycast/extensions PR #27308 was auto-closed for inactivity — reviving it as "Axle" risks the same flag). - name: axle -> asafamos-accessibility-scanner - title: "Axle — Accessibility Scanner" -> "AsafAmos — Accessibility Scanner" - command subtitles + README/CHANGELOG headers updated to match. - Kept references to the axle hosted backend (axle-iota.vercel.app) — that's the real API, not the listing identity (same approach as the WP plugin). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ No accessibility violations detectedScanned axe-core automated checks catch roughly 57% of WCAG issues. Manual review still recommended. Powered by axle · Remediation assistance, not compliance certification. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
WordPress.org's review flagged "Axle" as colliding with the existing "Axle AI" project — we renamed the WP plugin to AsafAmos Accessibility Scanner. The Raycast extension carried the same "Axle" name, and its
raycast/extensionsPR (#27308) was auto-closed for inactivity. Before reviving it, rename it the same way so it doesn't hit the same trademark flag.What
name:axle→asafamos-accessibility-scannertitle:Axle — Accessibility Scanner→AsafAmos — Accessibility Scanneraxle-iota.vercel.appbackend references — that's the real API, not the listing's brand identity (mirrors how the WP plugin keeps its hosted-service references).Note
This is the code rename only. Reviving the store listing still needs your hand: reopen/resubmit on
raycast/extensionsfrom your fork with the renamed extension.🤖 Generated with Claude Code