ramadhan sjamsani
2645bcd0e5
Verif Choice Sheet on display_name_screen drives the user into either the verified or anonymous onboarding sub-flow. ESP screen (12 chips, multi-select, info-only) + USP screen are shared between both branches; selections persist through to chat_sessions.topics on session start. OTP-blocked popup (HaloPopup) listens for the four real OTP-rate-limit error codes (OTP_RATE_LIMIT_PHONE, OTP_RATE_LIMIT_IP, OTP_COOLDOWN, OTP_ATTEMPTS_EXCEEDED) and drops the user onto the anonymous path with ESP/USP state preserved. Auth-providers gating replaces the --dart-define=ENABLE_SOCIAL_AUTH build flag with server-driven discovery. authProvidersProvider preloads GET /api/shared/auth-providers at cold start; welcome/register/ force-register screens render Google/Apple buttons only when the backend reports enabled:true. Falls back to phone-OTP-only when both providers are off. social_auth_enabled.dart deleted; client_app/CLAUDE.md updated to reflect the new gating contract. Mitra app: chat screen renders an ESP chip strip above the first message bubble when chat_sessions.topics is non-empty. Backend session.service.js getSessionById SELECTs cs.topics so the mitra side can read the customer's selected topics. Maestro flows 02_onboarding_verified.yaml + 03_onboarding_anon.yaml. Deviation from plan: plan referenced OTP error code 'otp_retry_exhausted'; real codes are OTP_RATE_LIMIT_*/OTP_COOLDOWN/OTP_ATTEMPTS_EXCEEDED - popup listens for all four. Plan said 'has_paid_first_session'; live endpoint returns 'has_consulted_before' - used the live field. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
13 lines
640 B
Dart
13 lines
640 B
Dart
import 'package:flutter_riverpod/flutter_riverpod.dart';
|
|
import 'esp_topic.dart';
|
|
|
|
/// Ephemeral selection from the ESP screen. Survives across the
|
|
/// onboarding flow (Verif Sheet → ESP → USP → OTP / Pilih cara). Cleared
|
|
/// when a chat session is created server-side.
|
|
final espSelectionProvider = StateProvider<Set<EspTopic>>((_) => <EspTopic>{});
|
|
|
|
/// Set to `true` when the user tapped "lewati" on the ESP screen. Distinct
|
|
/// from "user picked nothing then pressed Lanjut" — the backend wants to
|
|
/// know whether the empty set was intentional or a deliberate skip.
|
|
final espSkippedProvider = StateProvider<bool>((_) => false);
|