|
| 1 | +# UI component gaps (May 2026) |
| 2 | + |
| 3 | +Snapshot of RoxyAPI endpoints that have **no dedicated `@roxyapi/ui` component** as of the package's May 2026 component table. Consumers of `roxyapi/sdk` get raw JSON for these and must render manually (or fall back to `<roxy-data>`, the generic JSON renderer). |
| 4 | + |
| 5 | +This file is informational - it lives in the PHP SDK repo so the maintainer of [@roxyapi/ui](https://github.com/roxyapi/ui) has a running list without us polluting that repo's commits. |
| 6 | + |
| 7 | +## Current gaps |
| 8 | + |
| 9 | +| Domain | Endpoints | Status | |
| 10 | +|---|---|---| |
| 11 | +| Crystals (`/crystals/*`) | 12 endpoints (search, by zodiac, by chakra, by element, birthstone, daily, random, pairings, lookup, all, hardness, vibration) | No card / grid component | |
| 12 | +| Angel Numbers (`/angel-numbers/*`) | 4 endpoints (lookup, sequence analysis, daily, by type) | No card component | |
| 13 | +| Dreams (`/dreams/*`) | 5 endpoints (symbol, search, A-Z, random, popular) | No symbol-card / dictionary component | |
| 14 | +| Languages (`/languages`) | 1 endpoint (list supported response languages) | No selector helper component | |
| 15 | +| Usage (`/usage/*`) | 1 endpoint (current usage stats) | No usage-meter component | |
| 16 | +| Advanced KP | `/vedic-astrology/kp/{ruling-planets,ruling-planets-interval,sublord-changes,rasi-changes,planets-interval,ayanamsa,cusps,chart}` | Only `<roxy-kp-planets-table>` exists; ruling-planets / interval / sublord-changes have no dedicated view | |
| 17 | +| Vedic divisional listings | 15 divisional charts (D2 Hora through D60 Shashtiamsa) covered by one generic `<roxy-divisional-chart>`; per-varga deep-dive views (e.g. D9 Navamsa specific) do not exist | One-size-fits-all today | |
| 18 | +| Numerology helper views | `/numerology/{lucky-numbers,bridge-numbers,karmic-debt,karmic-lessons,subconscious-self,maturity-number,personality-number,birth-day,balance-number,challenges,pinnacles}` are folded under `<roxy-numerology-card>`; per-aspect breakdowns do not exist | Single-card aggregate today | |
| 19 | + |
| 20 | +## Decision tree for SDK consumers |
| 21 | + |
| 22 | +If your endpoint has a dedicated component: |
| 23 | +1. Fetch with the SDK server-side. |
| 24 | +2. Pass the JSON to the matching `<roxy-*>` element in the browser. |
| 25 | + |
| 26 | +If it does not (this list): |
| 27 | +1. Fetch with the SDK server-side. |
| 28 | +2. Either render manually (PHP -> HTML), or assign the JSON to `<roxy-data>` for a generic structured display. |
| 29 | + |
| 30 | +## How this list is maintained |
| 31 | + |
| 32 | +Manual diff of `specs/openapi.json` x the `BEGIN:COMPONENTS` table in the [@roxyapi/ui AGENTS.md](https://github.com/roxyapi/ui/blob/main/AGENTS.md). When `@roxyapi/ui` ships a new component for one of the gaps above, drop the row. |
0 commit comments