fix(GRO-765): portal appointments crash — incomplete service data + response shape #322

Closed

groombook-engineer[bot] wants to merge 3 commits from fix/gro-765-portal-appointments-service into main

Author	SHA1	Message	Date
Test User	71c5265da7	fix(GRO-682): pre-populate corepack cache at build time corepack prepare now runs during Docker build (both builder and runner stages) so the cache directory is populated before readOnlyRootFilesystem is enforced at runtime. Previously the mkdir existed without populating the cache, causing ENOENT errors in migrate/seed jobs. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-19 00:34:42 +00:00
Test User	dcb929be5b	fix(GRO-765): remove dead upcoming/past filter code in portal appointments The now/upcoming/past variables were unused after the response shape change to { appointments: appts }. QA flagged them as dead code. Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-17 17:22:41 +00:00
Test User	0ace23de53	fix(GRO-765): include service name in portal appointments response - Added service JOIN to /api/portal/appointments to include name, duration, and price fields in the service sub-object - Changed API response shape from { upcoming, past } to { appointments: [] } to match client expectations and simplify data flow - Updated Appointments, ReportCards, and Dashboard components to transform the new response format (startTime → date + time) and extract serviceName, petName, and groomerName from nested sub-objects Co-Authored-By: Paperclip <noreply@paperclip.ing>	2026-04-17 12:50:07 +00:00

Author

SHA1

Message

Date

Test User

71c5265da7

fix(GRO-682): pre-populate corepack cache at build time

corepack prepare now runs during Docker build (both builder and runner
stages) so the cache directory is populated before readOnlyRootFilesystem
is enforced at runtime. Previously the mkdir existed without populating
the cache, causing ENOENT errors in migrate/seed jobs.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-04-19 00:34:42 +00:00

Test User

dcb929be5b

fix(GRO-765): remove dead upcoming/past filter code in portal appointments

The now/upcoming/past variables were unused after the response shape
change to { appointments: appts }. QA flagged them as dead code.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-04-17 17:22:41 +00:00

Test User

0ace23de53

fix(GRO-765): include service name in portal appointments response

- Added service JOIN to /api/portal/appointments to include name, duration,
  and price fields in the service sub-object
- Changed API response shape from { upcoming, past } to { appointments: [] }
  to match client expectations and simplify data flow
- Updated Appointments, ReportCards, and Dashboard components to transform
  the new response format (startTime → date + time) and extract serviceName,
  petName, and groomerName from nested sub-objects

Co-Authored-By: Paperclip <noreply@paperclip.ing>

2026-04-17 12:50:07 +00:00

fix(GRO-765): portal appointments crash — incomplete service data + response shape #322

3 Commits