fix(customers): handle REJECTED verification explicitly

verifyStepOne() sent REJECTED to `default`, which returns 2
("accepted"). The admin list unlocks the order/account switches when
step one is 2, so a rejected customer would have had them unlocked.
REJECTED now maps to 3, matching legacy, where a step-one reject also
set active = -1.

Both switches are now exhaustive with no `default`, so a future enum
value fails the build instead of falling through silently.

Both user apps' ProfileView label it «رد شده». Before this they showed
the raw English value.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
s.esmaeili
2026-10-07 17:37:19 +03:30
co-authored by Claude Opus 5.5
parent 45633b5aa0
commit e020e6a633
3 changed files with 14 additions and 3 deletions
@@ -111,6 +111,7 @@ const VERIFICATION_LABELS: Record<string, string> = {
STEP_ONE_SUBMITTED: 'مرحله اول ثبت شده',
STEP_TWO_SUBMITTED: 'مرحله دوم ثبت شده',
VERIFIED: 'تایید شده',
REJECTED: 'رد شده',
}
const session = useSessionStore()