[hero_planner_server] system_counts returns conditions; clients expect necessary_conditions #26

Closed
opened 2026-06-14 16:25:21 +00:00 by sameh-farouk · 1 comment
Member

system_counts returns a conditions field for necessary-condition counts, but the entity is necessary_condition everywhere else (the web UI reads necessary_conditions). The web remap aliases it. Minor, but the field name should match the entity for API/SDK consistency.

`system_counts` returns a `conditions` field for necessary-condition counts, but the entity is `necessary_condition` everywhere else (the web UI reads `necessary_conditions`). The web remap aliases it. Minor, but the field name should match the entity for API/SDK consistency.
Author
Member

Fixed on development in 7976504 — renamed EntityCounts.conditionsnecessary_conditions in the .oschema + the system_counts impl (the entity is necessary_condition everywhere else; the web reads necessary_conditions).

Verified: system_counts(main) returns necessary_conditions: 3 (a real SQL COUNT(*)), no stale conditions key; the regenerated openrpc_main.json reflects it. Source-only.

Fixed on `development` in `7976504` — renamed `EntityCounts.conditions` → `necessary_conditions` in the `.oschema` + the `system_counts` impl (the entity is `necessary_condition` everywhere else; the web reads `necessary_conditions`). Verified: `system_counts(main)` returns `necessary_conditions: 3` (a real SQL `COUNT(*)`), no stale `conditions` key; the regenerated `openrpc_main.json` reflects it. Source-only.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
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_planner#26
No description provided.