Skip to content

Switched booking locations step to filtered offices-by-service API. - #1099

Merged
veenupunyani merged 1 commit into
developfrom
Use-services-by-location-API-endpoint-for-locations-page
Aug 25, 2026
Merged

Switched booking locations step to filtered offices-by-service API.#1099
veenupunyani merged 1 commit into
developfrom
Use-services-by-location-API-endpoint-for-locations-page

Conversation

@veenupunyani

Copy link
Copy Markdown
Collaborator

Summary

  • Added a booking service-locations API client that calls existing GET /api/v1/offices?service_id= and maps next_appointment_date (ISO) for later UI use.
  • Wired the locations step to load offices for the selected service only; kept the old all-locations client untouched.
  • Preserved existing SHOW / appointments-enabled client filters.

Test plan

If you have the same seed data from earlier PR's then,

  • Select Medical Services Plan Application for BC Medical -> locations list shows Test Office and Victoria only
  • Select Rural Property Tax - Deferment Application -> list shows 100 Mile House and Test Office only
  • Network tab: request is GET …/offices?service_id= (no trailing slash); response includes next_appointment_date

@sonarqubecloud

Copy link
Copy Markdown

@veenupunyani
veenupunyani merged commit d4281b8 into develop Aug 25, 2026
3 checks passed
@veenupunyani
veenupunyani deleted the Use-services-by-location-API-endpoint-for-locations-page branch September 1, 2026 20:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants