Skip to content

fix: derive artifact kind from the id prefix - #198

Merged
PhantomInTheWire merged 1 commit into
mainfrom
fix/kind-from-id-prefix
Aug 20, 2026
Merged

fix: derive artifact kind from the id prefix#198
PhantomInTheWire merged 1 commit into
mainfrom
fix/kind-from-id-prefix

Conversation

@PhantomInTheWire

@PhantomInTheWire PhantomInTheWire commented Aug 20, 2026

Copy link
Copy Markdown
Member

The wire carries no type field (verified against live production — the kind is the id prefix), so the item.type read never matched and the kind label silently never rendered. Derives it from the prefix instead, allowlisted to the four real kinds.

Aligned with today's docs (firecrawl-docs#1291) and blog fix.


Summary by cubic

Renders the artifact kind label in developer search results by deriving it from the id prefix. Previously we read item.type (not present on the wire), so the label never showed.

  • Derives kind from allowlisted prefixes: doc, issue, pull_request, readme; unknown prefixes omit the label.
  • UI-only change in src/commands/developer.ts; no API changes or migrations.

Written for commit a282a62. Summary will update on new commits.

Review in cubic

The developer-search wire carries no type field; the kind is encoded in
the id prefix (doc:, issue:, pull_request:, readme:). The old item.type
read matched nothing and the kind label silently never rendered.
@PhantomInTheWire
PhantomInTheWire merged commit dac8a0b into main Aug 20, 2026
8 checks passed
@PhantomInTheWire
PhantomInTheWire deleted the fix/kind-from-id-prefix branch August 20, 2026 17:16
@PhantomInTheWire PhantomInTheWire mentioned this pull request Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant