feat(booking): take service duration from the backend, not a parallel client sum

The service picker summed duration_minutes itself while the backend already
returns total_duration_minutes. Two sources of truth: when the formula changes to
solo/additional minutes, the site would keep showing the old number and the
patient would see a duration that does not match their appointment.

The picker runs before the date step and appointment-service-slots needs a date,
so it is called with today. total_duration_minutes does not depend on the date —
the backend computes it before touching that day's shifts, so the number is right
even when today is closed and start_times comes back empty.

The label reads "مدت تقریبی" until the server number arrives, then "مدت کل".
A missing field or a failed request falls back to the client sum with a
console.warn rather than blanking the step.

Staleness is derived from the selection key instead of reset in the effect body,
which also clears the set-state-in-effect lint warning.

Task: clinicpro/docs/new_feture/taskes/task-00b-nobat724-service-mode/

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

This commit is contained in:

hamed

2026-07-30 15:50:07 +03:30

co-authored by

Claude Opus 5

parent 29881eede0

commit f3659f827e

2 changed files with 57 additions and 6 deletions

									
										components/appointment/Container.js
									
		+2
		
												View File
												
				@@ -77,6 +77,8 @@ function Container({

				    dateStep = (

				      <ServiceSelect

				        services={bookingServices}

				        doctorUuid={doctor?.uuid}

				        clinicUuid={clinicUuid}

				        onContinue={(uuids) => setSelectedServiceUuids(uuids)}

				      />

				    );