The API reference on ipxreader.app has no Signals #269

Closed
opened 2026-10-16 13:48:47 -07:00 by rays · 1 comment
Owner

site/api.mjs, which ipxreader.app/docs/api is generated from, lists none of the Signals routes added in 1.3.0 (#254): GET/POST /api/signals, PATCH/DELETE /api/signals/{id}, GET /api/signals/{id}/entries, POST /api/signals/icon, nor typesafe_key on /api/me. Found while adding a Signals section to the home page.

site/api.mjs, which ipxreader.app/docs/api is generated from, lists none of the Signals routes added in 1.3.0 (#254): GET/POST /api/signals, PATCH/DELETE /api/signals/{id}, GET /api/signals/{id}/entries, POST /api/signals/icon, nor typesafe_key on /api/me. Found while adding a Signals section to the home page.
rays added the enhancement label 2026-10-16 13:48:47 -07:00
Author
Owner

Fixed in 026fbd1: the API reference has a Signals section (list, make, change, delete, a Signal's items, the icon pick) with the Signal, SignalBody and IconAsk types, and Me, MePatch, Settings and the events list have Signals' fields. Live on ipxreader.app.

Fixed in 026fbd1: the API reference has a Signals section (list, make, change, delete, a Signal's items, the icon pick) with the Signal, SignalBody and IconAsk types, and Me, MePatch, Settings and the events list have Signals' fields. Live on ipxreader.app.
rays closed this issue 2026-10-17 06:41:50 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#269