fix: align Flutter API repositories with backend routes (Fase 3 prep)

- api_service_repository: use correct endpoints (/services/me, /services/professional,
  /professional/requests, /professional/history, /professional/calendar)
  instead of broken /services?userId= query params
- api_service_repository: fix status string↔enum, createService DTO,
  paginated {data,meta} response, stub setProfessionalScored/setUserScored,
  extract professionalId from nested professionals.user_id
- api_score_repository: fix /comments/user/:id and /comments/professional/:id
- api_professional_repository + api_user_repository: handle paginated response

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Lizandro Guarnizo
2026-06-17 18:29:47 -05:00
co-authored by Claude Sonnet 4.6
parent af91e0ba04
commit 7fb0615169
4 changed files with 117 additions and 115 deletions
@@ -201,7 +201,8 @@ class ApiUserRepository implements UserRepository {
@override
Future<List<MyUser>> getUsersProfessionalActive() async {
try {
final data = await _get('/professionals') as List;
final body = await _get('/professionals');
final List data = body is Map ? (body['data'] as List? ?? []) : (body as List? ?? []);
final List<MyUser> result = [];
for (final p in data) {
final userId = p['user_id']?.toString();