Skip to content

rux get: no route for building components; --help lists collections that don't exist #354

Description

@pfmephisto

Found while building the MCP gateway (PR #349, #267).

Two related gaps in the path-based DB access:

  1. Building components have no `rux get` route. The real collections are `clouds, frames, labels, log, materials, meshes, panoramas, projects` — components are only reachable via `rux export csv`, which the MCP gateway now uses as a documented stopgap (`tools/rux-mcp/src/rux_mcp/components.py`).
  2. `rux get --help` is stale: it advertises `components` and `passports` as collections, but neither resolves (passports actually live under `materials`).

Fix: add a `components` router (`apps/rux/src/database/` — the 8 existing `*_router.cpp` files are the template, and since #249/#345 they are linkable from tests), and regenerate the help text from the actual router table so it cannot drift again.

category=CLI estimate=4h

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions