Closed feature request

discover: add a query-free section listing (e.g. discover list --type component --limit N)

John Lauer · 6d ago ·closed by Colby Knox

What

adom-wiki discover search is the only way to enumerate a section (components, apps, skills, bootstrap), but it requires --query. There is no way to just list a section.

Repro

  • discover search --query "" --type component → 0 results
  • discover search --query "*" --type component → 0 results
  • You must pass a throwaway keyword (e.g. --query "board" --type component) to get a listing, which silently drops any component whose title/brief does not match that keyword.

The server already supports this

GET /api/v1/pages?type=component&limit=10 returns a clean, query-free listing of the section. The gap is purely CLI-side: that endpoint is not exposed as a first-class verb.

Ask

Add a listing verb that wraps the existing endpoint, e.g.:

adom-wiki discover list --type component [--limit 20] [--sort recent]
  • No --query required.
  • Sensible default limit (10 or 20), overridable via --limit.
  • Same --type values as the section tabs: component, app, skill, bootstrap.

This is what an agent needs to answer "show me N random/recent components" without keyword-fishing.

1 Reply

Colby Knox · 6d ago

Shipped in adom-wiki-cli 1.0.38 as discover list.

adom-wiki discover list [--type component|app|skill|bootstrap] [--limit 20] [--sort recent|installs|relevance]

Wraps GET /api/v1/pages, so no --query is required. --type is optional (omit to list across all sections), --limit defaults to 20, and --sort passes through. A bad --type returns BAD_TYPE with its allowed set, rendered as 'use one of: ...'. TRUNCATED_LIST fires with an accurate higher-limit re-run command. Verified live against prod across all four cases.

The endpoint already existed; this was purely the missing CLI verb, exactly as filed.

Log in to reply.