Admin UI is broken: hero_books_admin has no /rpc proxy route #98

New issue

Closed

opened 2026-04-21 07:43:09 +00:00 by mahmoud · 4 comments

mahmoud commented 2026-04-21 07:43:09 +00:00

Owner

Copy link

Problem

The hero_books_admin dashboard UI is broken for all dynamic data. Every admin page fetches data via a JavaScript rpc() helper that POSTs to BASE_PATH + "/rpc" — but the admin router never registers a /rpc route, so every call returns 404.

Evidence

Templates call /rpc:

• crates/hero_books_admin/templates/base.html:111-123 defines the rpc() helper: fetch(BASE_PATH + "/rpc", { method: "POST", ... }).
• Seven call-sites use it:
  • templates/index.html:41 — rpc("libraries.list", {})
  • templates/index.html:55 — rpc("libraries.get", { name })
  • templates/collections.html:38 — rpc("collections.list", {})
  • templates/collections.html:89 — rpc("collections.get", { name })
  • templates/health.html:26 — rpc("server.health", {})
  • templates/import.html:52 — rpc("importservice.list_namespaces", {})
  • templates/import.html:85 — rpc("importservice.start", { request })
  • templates/export.html:108 — rpc("collections.exportToDir", params)

Admin router does not register /rpc:

crates/hero_books_admin/src/main.rs:244-253 registers /, /collections, /health, /.well-known/heroservice.json, /import, /export, /settings — no /rpc route, no /openrpc.json.

The admin home, Libraries, Collections, Import, Export, and Health pages all silently fail to load data in the browser.

Root cause

Violation of the hero_ui_openrpc_proxy skill: every Hero admin UI should expose a local /rpc endpoint that forwards JSON-RPC requests to the service's rpc.sock. hero_books_ui already has this (crates/hero_books_ui/src/proxy.rs::api_proxy); hero_books_admin was never given the equivalent.

Fix

Add an /rpc proxy handler to hero_books_admin that forwards POST bodies to $HERO_SOCKET_DIR/hero_books/rpc.sock and returns the JSON-RPC response verbatim. Mirror the pattern used in crates/hero_books_ui/src/proxy.rs:

1. New module crates/hero_books_admin/src/proxy.rs with a single async handler api_proxy.
2. Register .route("/rpc", post(api_proxy)) in main.rs alongside the existing GET routes.
3. Preserve header forwarding: X-Forwarded-Prefix, X-Hero-Context, X-Hero-Claims.
4. Return 502 on upstream failure with a clear message (not 500 — the admin server itself is fine, the upstream is what's unavailable).

Acceptance criteria

• POST /rpc on the admin socket forwards to hero_books/rpc.sock and returns the JSON-RPC response.
• Opening the admin home in a browser loads the libraries list without 404s in the network tab.
• Opening Collections, Import, Export, and Health likewise loads their data.
• X-Forwarded-Prefix is preserved on the forwarded request (so URL generation in the server still works).
• A unit or integration test that POSTs to /rpc and verifies the round-trip path.

Scope

Small — one new module, one new route, tests. No schema or RPC-surface changes. Local to hero_books_admin.

## Problem The `hero_books_admin` dashboard UI is broken for all dynamic data. Every admin page fetches data via a JavaScript `rpc()` helper that POSTs to `BASE_PATH + "/rpc"` — but the admin router never registers a `/rpc` route, so every call returns **404**. ## Evidence **Templates call `/rpc`:** - `crates/hero_books_admin/templates/base.html:111-123` defines the `rpc()` helper: `fetch(BASE_PATH + "/rpc", { method: "POST", ... })`. - Seven call-sites use it: - `templates/index.html:41` — `rpc("libraries.list", {})` - `templates/index.html:55` — `rpc("libraries.get", { name })` - `templates/collections.html:38` — `rpc("collections.list", {})` - `templates/collections.html:89` — `rpc("collections.get", { name })` - `templates/health.html:26` — `rpc("server.health", {})` - `templates/import.html:52` — `rpc("importservice.list_namespaces", {})` - `templates/import.html:85` — `rpc("importservice.start", { request })` - `templates/export.html:108` — `rpc("collections.exportToDir", params)` **Admin router does not register `/rpc`:** `crates/hero_books_admin/src/main.rs:244-253` registers `/`, `/collections`, `/health`, `/.well-known/heroservice.json`, `/import`, `/export`, `/settings` — **no `/rpc` route, no `/openrpc.json`**. The admin home, Libraries, Collections, Import, Export, and Health pages all silently fail to load data in the browser. ## Root cause Violation of the [`hero_ui_openrpc_proxy`](https://forge.ourworld.tf/lhumina_code/hero_skills/src/branch/main/claude/skills/hero_ui_openrpc_proxy/SKILL.md) skill: every Hero admin UI should expose a local `/rpc` endpoint that forwards JSON-RPC requests to the service's `rpc.sock`. `hero_books_ui` already has this (`crates/hero_books_ui/src/proxy.rs::api_proxy`); `hero_books_admin` was never given the equivalent. ## Fix Add an `/rpc` proxy handler to `hero_books_admin` that forwards POST bodies to `$HERO_SOCKET_DIR/hero_books/rpc.sock` and returns the JSON-RPC response verbatim. Mirror the pattern used in `crates/hero_books_ui/src/proxy.rs`: 1. New module `crates/hero_books_admin/src/proxy.rs` with a single async handler `api_proxy`. 2. Register `.route("/rpc", post(api_proxy))` in `main.rs` alongside the existing GET routes. 3. Preserve header forwarding: `X-Forwarded-Prefix`, `X-Hero-Context`, `X-Hero-Claims`. 4. Return 502 on upstream failure with a clear message (not 500 — the admin server itself is fine, the upstream is what's unavailable). ## Acceptance criteria - [ ] `POST /rpc` on the admin socket forwards to `hero_books/rpc.sock` and returns the JSON-RPC response. - [ ] Opening the admin home in a browser loads the libraries list without 404s in the network tab. - [ ] Opening Collections, Import, Export, and Health likewise loads their data. - [ ] `X-Forwarded-Prefix` is preserved on the forwarded request (so URL generation in the server still works). - [ ] A unit or integration test that POSTs to `/rpc` and verifies the round-trip path. ## Scope Small — one new module, one new route, tests. No schema or RPC-surface changes. Local to `hero_books_admin`.

mahmoud commented 2026-04-21 07:54:13 +00:00

Author

Owner

Copy link

Implementation Spec for Issue #98

Objective

Add a /rpc proxy route to hero_books_admin that forwards POST bodies to $HERO_SOCKET_DIR/hero_books/rpc.sock, matching the pattern used in hero_books_ui.

Requirements

• New /rpc route wired into the admin router.
• Upstream socket resolved via hero_books_lib::default_server_socket_path() with HERO_BOOKS_SOCKET env override — same resolution as hero_books_ui.
• X-Forwarded-Prefix, X-Hero-Context, X-Hero-Claims propagation already lives in admin middleware; proxy forwards Content-Type and Authorization like the reference.
• Upstream connection failures return HTTP 502, not 500.
• No changes to hero_books_server, hero_books_ui, or other crates.

Files to Modify/Create

• crates/hero_books_admin/src/proxy.rs — new module, copied from crates/hero_books_ui/src/proxy.rs with admin-duplicated items trimmed.
• crates/hero_books_admin/src/main.rs — add mod proxy;, construct AppState, register /rpc route, attach state via .with_state(state).
• crates/hero_books_admin/Cargo.toml — no new dependencies required.

Implementation Plan

Step 1: Create crates/hero_books_admin/src/proxy.rs

Files: crates/hero_books_admin/src/proxy.rs

• Copy crates/hero_books_ui/src/proxy.rs verbatim.
• Delete items already defined in admin's main.rs: BasePath, HeroRequestContext, base_path_middleware.
• Keep: AppState, proxy_request, api_proxy. Drop img_proxy and pdf_proxy if present (admin templates have no image/pdf fetches).
• Keep the function name api_proxy verbatim.
• Do not restyle or rename retained code.
  Dependencies: none.

Step 2: Wire proxy into admin router

Files: crates/hero_books_admin/src/main.rs

• Add mod proxy; near the top.
• Add imports: axum::routing::any, proxy::{AppState, api_proxy}, std::sync::Arc.
• Keep admin's existing local BasePath/HeroRequestContext/base_path_middleware — do not remove or rename.
• In run_serve, before building the router:
  • Resolve upstream socket: prefer std::env::var("HERO_BOOKS_SOCKET"), else hero_books_lib::default_server_socket_path().to_string_lossy().to_string().
  • Build let state = AppState { server_socket: Arc::new(server_socket) };.
• In the Router::new() chain, add .route("/rpc", any(api_proxy)) before the .layer(...) calls.
• After the .layer(cors) line, add .with_state(state).
  Dependencies: Step 1.

Step 3: Smoke test

Files: crates/hero_books_admin/tests/rpc_proxy.rs (new) or inline #[cfg(test)] in proxy.rs.

• Spawn a stub Unix-socket HTTP listener bound to a tempdir path that responds 200 with a fixed JSON body.
• Build Router::new().route("/rpc", any(api_proxy)).with_state(AppState{ server_socket: Arc::new(tmp_sock) }).
• Drive it via tower::ServiceExt::oneshot with a POST /rpc carrying a JSON-RPC body; assert the body round-trips verbatim and the status is 200.
• Second test: point server_socket at a non-existent path, assert status is 502.
  Dependencies: Step 2.

Step 4: Manual verification

• cargo build -p hero_books_admin and cargo clippy -p hero_books_admin -- -D warnings.
• Start the full stack (hero_books --start), load an admin page (/collections), confirm the XHR to /rpc returns 200 and populates the table.
  Dependencies: Step 3.

Acceptance Criteria

• POST /rpc on the admin socket forwards to hero_books/rpc.sock and returns the body verbatim
• Upstream failure returns 502 with a descriptive error (not 500)
• X-Forwarded-Prefix, X-Hero-Context, X-Hero-Claims forwarded (already handled by existing admin middleware — unchanged)
• Unit or integration test covering the round-trip
• Build + clippy clean
• No changes to hero_books_server, hero_books_ui, or other crates

Notes

• hero_books_ui already uses a hand-rolled proxy.rs. Staying consistent with the sibling crate is the correct call here; migrating both crates to the openrpc_proxy! macro would be a separate, larger refactor.
• No dependency additions needed — hyper, hyper-util, http-body-util, tower, and tokio are already in hero_books_admin/Cargo.toml.
• The admin's existing BasePath/HeroRequestContext/base_path_middleware are functionally identical to the hero_books_ui versions but live in main.rs. Leave them in place to minimize diff surface.
• api_proxy handles any HTTP method, so registering with any(api_proxy) matches the UI and covers future GET-style discovery the templates might add.

## Implementation Spec for Issue #98 ### Objective Add a `/rpc` proxy route to `hero_books_admin` that forwards POST bodies to `$HERO_SOCKET_DIR/hero_books/rpc.sock`, matching the pattern used in `hero_books_ui`. ### Requirements - New `/rpc` route wired into the admin router. - Upstream socket resolved via `hero_books_lib::default_server_socket_path()` with `HERO_BOOKS_SOCKET` env override — same resolution as `hero_books_ui`. - `X-Forwarded-Prefix`, `X-Hero-Context`, `X-Hero-Claims` propagation already lives in admin middleware; proxy forwards `Content-Type` and `Authorization` like the reference. - Upstream connection failures return HTTP 502, not 500. - No changes to `hero_books_server`, `hero_books_ui`, or other crates. ### Files to Modify/Create - `crates/hero_books_admin/src/proxy.rs` — new module, copied from `crates/hero_books_ui/src/proxy.rs` with admin-duplicated items trimmed. - `crates/hero_books_admin/src/main.rs` — add `mod proxy;`, construct `AppState`, register `/rpc` route, attach state via `.with_state(state)`. - `crates/hero_books_admin/Cargo.toml` — no new dependencies required. ### Implementation Plan #### Step 1: Create `crates/hero_books_admin/src/proxy.rs` Files: `crates/hero_books_admin/src/proxy.rs` - Copy `crates/hero_books_ui/src/proxy.rs` verbatim. - Delete items already defined in admin's `main.rs`: `BasePath`, `HeroRequestContext`, `base_path_middleware`. - Keep: `AppState`, `proxy_request`, `api_proxy`. Drop `img_proxy` and `pdf_proxy` if present (admin templates have no image/pdf fetches). - Keep the function name `api_proxy` verbatim. - Do not restyle or rename retained code. Dependencies: none. #### Step 2: Wire proxy into admin router Files: `crates/hero_books_admin/src/main.rs` - Add `mod proxy;` near the top. - Add imports: `axum::routing::any`, `proxy::{AppState, api_proxy}`, `std::sync::Arc`. - Keep admin's existing local `BasePath`/`HeroRequestContext`/`base_path_middleware` — do not remove or rename. - In `run_serve`, before building the router: - Resolve upstream socket: prefer `std::env::var("HERO_BOOKS_SOCKET")`, else `hero_books_lib::default_server_socket_path().to_string_lossy().to_string()`. - Build `let state = AppState { server_socket: Arc::new(server_socket) };`. - In the `Router::new()` chain, add `.route("/rpc", any(api_proxy))` before the `.layer(...)` calls. - After the `.layer(cors)` line, add `.with_state(state)`. Dependencies: Step 1. #### Step 3: Smoke test Files: `crates/hero_books_admin/tests/rpc_proxy.rs` (new) or inline `#[cfg(test)]` in `proxy.rs`. - Spawn a stub Unix-socket HTTP listener bound to a tempdir path that responds 200 with a fixed JSON body. - Build `Router::new().route("/rpc", any(api_proxy)).with_state(AppState{ server_socket: Arc::new(tmp_sock) })`. - Drive it via `tower::ServiceExt::oneshot` with a `POST /rpc` carrying a JSON-RPC body; assert the body round-trips verbatim and the status is 200. - Second test: point `server_socket` at a non-existent path, assert status is 502. Dependencies: Step 2. #### Step 4: Manual verification - `cargo build -p hero_books_admin` and `cargo clippy -p hero_books_admin -- -D warnings`. - Start the full stack (`hero_books --start`), load an admin page (`/collections`), confirm the XHR to `/rpc` returns 200 and populates the table. Dependencies: Step 3. ### Acceptance Criteria - [ ] POST /rpc on the admin socket forwards to `hero_books/rpc.sock` and returns the body verbatim - [ ] Upstream failure returns 502 with a descriptive error (not 500) - [ ] X-Forwarded-Prefix, X-Hero-Context, X-Hero-Claims forwarded (already handled by existing admin middleware — unchanged) - [ ] Unit or integration test covering the round-trip - [ ] Build + clippy clean - [ ] No changes to `hero_books_server`, `hero_books_ui`, or other crates ### Notes - `hero_books_ui` already uses a hand-rolled `proxy.rs`. Staying consistent with the sibling crate is the correct call here; migrating both crates to the `openrpc_proxy!` macro would be a separate, larger refactor. - No dependency additions needed — `hyper`, `hyper-util`, `http-body-util`, `tower`, and `tokio` are already in `hero_books_admin/Cargo.toml`. - The admin's existing `BasePath`/`HeroRequestContext`/`base_path_middleware` are functionally identical to the `hero_books_ui` versions but live in `main.rs`. Leave them in place to minimize diff surface. - `api_proxy` handles any HTTP method, so registering with `any(api_proxy)` matches the UI and covers future `GET`-style discovery the templates might add.

mahmoud commented 2026-04-21 08:25:45 +00:00

Author

Owner

Copy link

Test Results

Build

• cargo build -p hero_books_admin — ok

Clippy (warnings-as-errors)

• cargo clippy -p hero_books_admin -- -D warnings — clean
• cargo clippy -p hero_books_admin --tests -- -D warnings — clean

Tests

• hero_books_admin — Total: 2, Passed: 2, Failed: 0
  • tests/rpc_proxy.rs::round_trip_ok — ok
  • tests/rpc_proxy.rs::upstream_unreachable_returns_502 — ok
  • (unit tests in src/main.rs: 0 tests)
• hero_books_server (regression gate, unchanged) — Total: 16, Passed: 16, Failed: 0

Format

• cargo fmt --check -p hero_books_admin — applied (one reformat during this run; final check clean)

Notes

• Initial integration-test run failed with SUN_LEN on macOS because std::env::temp_dir() resolves to /var/folders/..., which exceeds the 104-byte Unix-socket path limit. The test helper was updated to root its per-run directory at /tmp and use a shorter hbadm_ prefix. After the fix both integration tests pass and fmt/clippy remain clean.

## Test Results ### Build - `cargo build -p hero_books_admin` — ok ### Clippy (warnings-as-errors) - `cargo clippy -p hero_books_admin -- -D warnings` — clean - `cargo clippy -p hero_books_admin --tests -- -D warnings` — clean ### Tests - `hero_books_admin` — Total: 2, Passed: 2, Failed: 0 - `tests/rpc_proxy.rs::round_trip_ok` — ok - `tests/rpc_proxy.rs::upstream_unreachable_returns_502` — ok - (unit tests in `src/main.rs`: 0 tests) - `hero_books_server` (regression gate, unchanged) — Total: 16, Passed: 16, Failed: 0 ### Format - `cargo fmt --check -p hero_books_admin` — applied (one reformat during this run; final check clean) ### Notes - Initial integration-test run failed with `SUN_LEN` on macOS because `std::env::temp_dir()` resolves to `/var/folders/...`, which exceeds the 104-byte Unix-socket path limit. The test helper was updated to root its per-run directory at `/tmp` and use a shorter `hbadm_` prefix. After the fix both integration tests pass and fmt/clippy remain clean.

mahmoud commented 2026-04-21 08:27:21 +00:00

Author

Owner

Copy link

Implementation Summary

The admin /rpc proxy is wired up on branch development_fix_admin_rpc_proxy. Every admin page can now round-trip JSON-RPC through the admin socket into hero_books_server.

Changes

• crates/hero_books_admin/src/proxy.rs (new) — copied verbatim from crates/hero_books_ui/src/proxy.rs, with img_proxy, pdf_proxy, and the items admin already defines (BasePath, HeroRequestContext, base_path_middleware) removed. Retains AppState, proxy_request, api_proxy byte-identical to the UI version, including the 502-on-upstream-failure behaviour and the Content-Type / Authorization request-header allowlist.
• crates/hero_books_admin/src/main.rs — added mod proxy;, imports for axum::routing::any, proxy::{AppState, api_proxy}, std::sync::Arc; resolved the upstream socket (HERO_BOOKS_SOCKET env, falling back to hero_books_lib::default_server_socket_path()); constructed proxy_state = AppState { server_socket: Arc::new(...) }; merged a small sub-router Router::new().route("/rpc", any(api_proxy)).with_state(proxy_state) into the main admin router so admin's own Router<()> state stays untouched.
• crates/hero_books_admin/tests/rpc_proxy.rs (new) — integration test covering both paths. round_trip_ok spawns a stub Unix-socket HTTP listener, fires POST /rpc via tower::ServiceExt::oneshot, and verifies the JSON body round-trips verbatim. upstream_unreachable_returns_502 points server_socket at a non-existent path and asserts HTTP 502.
• crates/hero_books_admin/Cargo.toml — added a [dev-dependencies] section with tower = { version = "0.5", features = ["util"] } so the integration test can call oneshot.

macOS note

The integration test roots its per-run tempdir under /tmp rather than std::env::temp_dir(). macOS resolves the latter to /var/folders/..., which blows past the 104-byte SUN_LEN limit once you append a subdirectory and a socket filename. A short doc comment in the test explains the constraint.

Test Results

• Build: cargo build -p hero_books_admin — ok.
• Clippy (warnings-as-errors): cargo clippy -p hero_books_admin -- -D warnings and --tests -- -D warnings — clean.
• hero_books_admin tests: 2/2 passed (round_trip_ok, upstream_unreachable_returns_502).
• hero_books_server library regression gate: 16/16 passed.
• cargo fmt --check -p hero_books_admin — clean after initial fmt application.

Acceptance criteria

• POST /rpc on the admin socket forwards to hero_books/rpc.sock and returns the body verbatim.
• Upstream failure returns HTTP 502, not 500.
• X-Forwarded-Prefix, X-Hero-Context, X-Hero-Claims forwarded (handled unchanged by the existing admin middleware).
• Integration test covering the round-trip.
• Build + clippy + fmt clean.
• No changes to hero_books_server, hero_books_ui, or other crates.

Follow-ups not in this PR

• Migrating both hero_books_ui and hero_books_admin to the openrpc_proxy! macro (current manual proxy.rs matches the sibling crate; macro migration is a bigger refactor and out of scope here).
• The other two items from the broader audit — consolidating architecture.md and adding docs/manual/docusaurus.md — remain open as docs-only follow-ups.

## Implementation Summary The admin `/rpc` proxy is wired up on branch `development_fix_admin_rpc_proxy`. Every admin page can now round-trip JSON-RPC through the admin socket into `hero_books_server`. ### Changes - **`crates/hero_books_admin/src/proxy.rs`** (new) — copied verbatim from `crates/hero_books_ui/src/proxy.rs`, with `img_proxy`, `pdf_proxy`, and the items admin already defines (`BasePath`, `HeroRequestContext`, `base_path_middleware`) removed. Retains `AppState`, `proxy_request`, `api_proxy` byte-identical to the UI version, including the 502-on-upstream-failure behaviour and the `Content-Type` / `Authorization` request-header allowlist. - **`crates/hero_books_admin/src/main.rs`** — added `mod proxy;`, imports for `axum::routing::any`, `proxy::{AppState, api_proxy}`, `std::sync::Arc`; resolved the upstream socket (`HERO_BOOKS_SOCKET` env, falling back to `hero_books_lib::default_server_socket_path()`); constructed `proxy_state = AppState { server_socket: Arc::new(...) }`; merged a small sub-router `Router::new().route("/rpc", any(api_proxy)).with_state(proxy_state)` into the main admin router so admin's own `Router<()>` state stays untouched. - **`crates/hero_books_admin/tests/rpc_proxy.rs`** (new) — integration test covering both paths. `round_trip_ok` spawns a stub Unix-socket HTTP listener, fires `POST /rpc` via `tower::ServiceExt::oneshot`, and verifies the JSON body round-trips verbatim. `upstream_unreachable_returns_502` points `server_socket` at a non-existent path and asserts HTTP 502. - **`crates/hero_books_admin/Cargo.toml`** — added a `[dev-dependencies]` section with `tower = { version = "0.5", features = ["util"] }` so the integration test can call `oneshot`. ### macOS note The integration test roots its per-run tempdir under `/tmp` rather than `std::env::temp_dir()`. macOS resolves the latter to `/var/folders/...`, which blows past the 104-byte `SUN_LEN` limit once you append a subdirectory and a socket filename. A short doc comment in the test explains the constraint. ### Test Results - Build: `cargo build -p hero_books_admin` — ok. - Clippy (warnings-as-errors): `cargo clippy -p hero_books_admin -- -D warnings` and `--tests -- -D warnings` — clean. - `hero_books_admin` tests: 2/2 passed (`round_trip_ok`, `upstream_unreachable_returns_502`). - `hero_books_server` library regression gate: 16/16 passed. - `cargo fmt --check -p hero_books_admin` — clean after initial fmt application. ### Acceptance criteria - [x] POST `/rpc` on the admin socket forwards to `hero_books/rpc.sock` and returns the body verbatim. - [x] Upstream failure returns HTTP 502, not 500. - [x] `X-Forwarded-Prefix`, `X-Hero-Context`, `X-Hero-Claims` forwarded (handled unchanged by the existing admin middleware). - [x] Integration test covering the round-trip. - [x] Build + clippy + fmt clean. - [x] No changes to `hero_books_server`, `hero_books_ui`, or other crates. ### Follow-ups not in this PR - Migrating both `hero_books_ui` and `hero_books_admin` to the `openrpc_proxy!` macro (current manual `proxy.rs` matches the sibling crate; macro migration is a bigger refactor and out of scope here). - The other two items from the broader audit — consolidating `architecture.md` and adding `docs/manual/docusaurus.md` — remain open as docs-only follow-ups.

mahmoud referenced this issue from a commit 2026-04-21 08:30:58 +00:00

fix(admin): add /rpc proxy route so the admin UI can reach the server

mahmoud referenced this issue 2026-04-21 08:31:19 +00:00

fix(admin): add /rpc proxy route so the admin UI can reach the server #99

mahmoud commented 2026-04-21 08:32:16 +00:00

Author

Owner

Copy link

Pull request opened: #99

This PR implements the changes discussed in this issue.

Pull request opened: https://forge.ourworld.tf/lhumina_code/hero_books/pulls/99 This PR implements the changes discussed in this issue.

mahmoud closed this issue 2026-04-21 10:00:32 +00:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

development

development_docs_rpc_methods

development_mik_nu_demo

development_expose_docusaurus_openrpc_async_jobs

development_mik2

main

v0.1.5

v0.1.4

v0.1.3

v0.1.2

v0.1.1

v0.1.0

v0.0.1-rc1

Labels

Clear labels   

prio_critical

  

prio_low

  

type_bug

  

type_contact

  

type_issue

  

type_lead

  

type_question

  

type_story

  

type_task

No labels

prio_critical

prio_low

type_bug

type_contact

type_issue

type_lead

type_question

type_story

type_task

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

lhumina_code/hero_books#98

No description provided.