6 Commits

Include renames

Author	SHA1	Message	Date
Lizandro GuarnizoandClaude Opus 5	389f876cfa	fix: repair the booking flow end to end ... Verified the real contracts against the backend before changing anything. Chat (three defects, one root cause): - every chat endpoint is keyed by the chat id, not the service id. The app called POST /chat/start, threw away the id it returned and kept using the service id, so every later request 404'd. - messages arrive as {data, meta}; reading the body as a bare list threw and surfaced as an empty conversation. - the bloc created the chat and then never emitted ChatLoaded (the else hung off `if (chat == null)`), leaving a permanent spinner. Sending a message emitted nothing at all, so it vanished until reopening. Messages now render optimistically and roll back if the send fails, and the screen distinguishes "loading" from "could not open" with a retry. Appointments: - a null range1_hour2 parsed as 00:00, so new appointments were born "Caducado" and every action was hidden. It now falls back to the start time. - service requests validate the HTTP status and tolerate an empty body: a 4xx was treated as success and a 204 as failure. - creating a service with no id in the response no longer reports success and navigates to a service that does not exist. - dispatching LoadService from build() looped forever on failure; the three detail screens now load once and offer a retry. Ratings: - both sides read userScored, so only one of the two could ever rate. The client side now reads professionalScored. - the screen closed before the request finished, killing the provider mid flight while addComment swallowed every error. It now waits for confirmation. - score/reputation parsing tolerates integers and numeric strings instead of emptying the review list. Also: guarded map lookups in ScoreBloc, a nullable name in the search list, and error states with retry where a failure used to shimmer forever. Verified against the backend: `accepted` is the status the API expects, so the suspected spelling bug was a false alarm and was left alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-24 20:47:54 -05:00
Lizandro GuarnizoandClaude Opus 5	8631e6f729	fix: port 7 web features and repair the endless-loading screens ... Root cause behind most "stuck loading" reports: the backend changed shape (schedules became an array, location_preferences a string) while the mobile parser still hard-cast to Map/int. The TypeError was swallowed by a silent catch that returned null, and screens only handled the success state, so a parse failure rendered as a permanent spinner. Same class of bug appeared across service lists via non-null map lookups and a total absence of request timeouts. Ported from prosappweb: - in-app suggestions (POST /suggestions) - policies/terms from GET /settings/policies - configurable appointment length (slot_duration_minutes) - block/unblock calendar slots (POST /services/block) - GPS city detection on the profile (Nominatim) - server-side professional search with haversine distance - retry cooldown after a rejected professional application Reliability: - parse schedules array (day_of_week 0=Mon) and string location_preferences - read times as wall clock, so 08:00 stays 08:00 across timezones - carry minutes into hours in TimeOfDay.add; a minute-based step used to loop forever and freeze the calendar (covered by test/time_slots_test.dart) - semver update check instead of string equality, which blocked every build that did not exactly match the configured version - request timeouts across all repositories - surface HTTP >= 400 instead of reporting failed writes as success - error states with retry instead of an indefinite shimmer Includes pre-existing uncommitted work from the UI redesign. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-24 16:45:42 -05:00
Lizandro GuarnizoandClaude Sonnet 4.6	90aab51a26	fix: remove Firebase repository exports from all 8 package barrel files ... Deleted firebase_*_repository.dart files were still re-exported, causing compile errors. Barrel files now only export the API implementations. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-18 12:24:48 -05:00
Lizandro GuarnizoandClaude Sonnet 4.6	af91e0ba04	chore: remove Firebase dependencies and legacy code (Fase 4) ... - Delete all firebase_*_repository.dart files (replaced by api_* equivalents) - Remove cloud_firestore, firebase_auth, firebase_storage, firebase_core from all package pubspecs - Remove cloud_firestore from main pubspec.yaml - Delete firebase_options.dart (no longer referenced) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 18:11:31 -05:00
Lizandro GuarnizoandClaude Sonnet 4.6	733384091c	feat: migrate prosappco from Firebase to NestJS REST API (Fase 2) ... - Replace all Firebase* repositories with Api* repositories using HTTP + SharedPreferences JWT - Remove Firebase.initializeApp() and firebase_messaging background handler from main.dart - Update DI (app_di.dart) to inject Api* repositories instead of Firebase* ones - Replace all Timestamp/cloud_firestore usage with ISO 8601 String dates - Stub PhoneVerificationService (Firebase phone OTP → backend OTP when implemented) - Add ApiService singleton with JWT management in lib/services/ - Legacy firebase_*_repository.dart files preserved for Fase 4 cleanup Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-17 16:53:11 -05:00
Felipe	61d517aaea	chat screen	2024-04-16 08:46:06 -05:00