fix(calendar): /auth/users path + Z-suffix appointment timestamps #65

Merged

YousifShkara merged 1 commit from fix/calendar-fetch-paths-and-tz-encoding into main

2026-06-05 09:59:06 +02:00

YousifShkara commented

2026-06-05 09:58:49 +02:00

Owner

Two failures on /calendar:

GET /api/v1/users?per_page=100 returned 404. The mokosh-server users CRUD lives at /api/v1/auth/users (nested under the auth router); the SPA had been calling the wrong path.

GET /api/v1/calendar/appointments?from=...&to=... returned 400. DateTime::<Utc>::to_rfc3339() emits 2026-05-31T04:00:00+00:00, and the literal + in a query string URL-decodes to a space, so the server's chrono parser saw 2026-05-31T04:00:00 00:00 and rejected the request. Switch to to_rfc3339_opts(SecondsFormat::Secs, true) which emits the Z suffix and round-trips cleanly without percent-encoding.

Both bugs surfaced together because the calendar page issues both calls on first mount.

Two failures on `/calendar`: `GET /api/v1/users?per_page=100` returned 404. The mokosh-server users CRUD lives at `/api/v1/auth/users` (nested under the auth router); the SPA had been calling the wrong path. `GET /api/v1/calendar/appointments?from=...&to=...` returned 400. `DateTime::<Utc>::to_rfc3339()` emits `2026-05-31T04:00:00+00:00`, and the literal `+` in a query string URL-decodes to a space, so the server's chrono parser saw `2026-05-31T04:00:00 00:00` and rejected the request. Switch to `to_rfc3339_opts(SecondsFormat::Secs, true)` which emits the `Z` suffix and round-trips cleanly without percent-encoding. Both bugs surfaced together because the calendar page issues both calls on first mount.

YousifShkara self-assigned this

2026-06-05 09:58:49 +02:00

YousifShkara added 1 commit

2026-06-05 09:58:49 +02:00

fix(calendar): /auth/users path + Z-suffix appointment timestamps

Create release / Create release from merged PR (pull_request) Has been skipped

Details

Check / clippy + fmt + tests (pull_request) Successful in 1m11s

Details

e5a92695fa

Two failures on `/calendar`:

`GET /api/v1/users?per_page=100` returned 404. The mokosh-server users CRUD lives at `/api/v1/auth/users` (nested under the auth router); the SPA had been calling the wrong path.

`GET /api/v1/calendar/appointments?from=...&to=...` returned 400. `DateTime::<Utc>::to_rfc3339()` emits `2026-05-31T04:00:00+00:00`, and the literal `+` in a query string URL-decodes to a space, so the server's chrono parser saw `2026-05-31T04:00:00 00:00` and rejected the request. Switch to `to_rfc3339_opts(SecondsFormat::Secs, true)` which emits the `Z` suffix and round-trips cleanly without percent-encoding.

Both bugs surfaced together because the calendar page issues both calls on first mount.

YousifShkara merged commit 9fa67b2941 into main

2026-06-05 09:59:06 +02:00

YousifShkara deleted branch fix/calendar-fetch-paths-and-tz-encoding

2026-06-05 09:59:06 +02:00

YousifShkara referenced this pull request from a commit

2026-06-05 09:59:07 +02:00

Merge pull request 'fix(calendar): /auth/users path + Z-suffix appointment timestamps' (#65) from fix/calendar-fetch-paths-and-tz-encoding into main

YousifShkara referenced this pull request from a commit

2026-06-05 10:07:50 +02:00

fix(calendar): create/update/delete via /appointments, role-gate users fetch

YousifShkara referenced this pull request

2026-06-05 10:09:26 +02:00