No description
Find a file
Ashwin Kumar ab25f7a994 feat(users): profile save, submit-for-verification, verification status endpoints
- profile.rs: GET/PATCH /api/profile, POST /api/profile/submit-for-verification,
  GET /api/me/verification-status — all role-aware, guards against duplicate pending
- verifications.rs: add POST /api/admin/verifications/:id/request-documents,
  fix RoleRepository/wallet_id match arm type errors
- coupons.rs: fix update_discount missing match block and i64/i32 type mismatch
- main.rs: mount /api/profile and /api/me verification-status routers

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-06 17:20:49 +02:00
apps feat(users): profile save, submit-for-verification, verification status endpoints 2026-04-06 17:20:49 +02:00
crates feat: complete backend implementation - payments service, admin endpoints, auth guards, submit-for-verification for all roles 2026-04-06 06:19:10 +02:00
docs chore: bootstrap rust backend workspace and migration master plan 2026-03-16 22:23:58 +01:00
scripts feat: add KB and support ticket system 2026-04-02 13:36:12 +02:00
.env.example feat(backend): enforce profile approvals and complete migration approval flows 2026-03-19 00:30:23 +01:00
.gitignore feat: add Redis for OTP, auth tokens, rate limiting, lead dedup and marketplace cache 2026-03-18 22:58:42 +01:00
Cargo.toml feat: complete backend implementation - payments service, admin endpoints, auth guards, submit-for-verification for all roles 2026-04-06 06:19:10 +02:00
docker-compose.yml feat: complete rust microservices migration with real db logic 2026-03-17 20:42:51 +01:00
README.md chore: bootstrap rust backend workspace and migration master plan 2026-03-16 22:23:58 +01:00
start-services.sh chore: update service startup script 2026-04-06 01:47:10 +02:00

NXTGAUGE Backend Rust

Rust migration target for nxtgauge-nov-2025-backend, preserving the same microservices and request flow.

Target Service Topology

  • gateway (HTTP API)
  • users (identity, runtime roles, onboarding, approvals)
  • companies
  • customers
  • professionals
  • jobseekers

Migration Policy

  • Keep contracts stable (REST + proto semantics).
  • Keep runtime-config and onboarding schema behavior unchanged during parity phases.
  • Replace service implementations one by one.

See docs/MIGRATION_MASTER_PLAN.md for full staged plan.