feat(leads+verification): wire Leads & Lead Verification to be-crm data door #35

2026-07-24T09:55:59Z

Mayur7887 commented

2026-07-24 09:55:59 +00:00

Integrates the Leads and Lead Verification screens with the live be-crm
backend (crm.lead.* / crm.leadVerification.* / crm.media.*) behind a
mode-agnostic data layer that still falls back to the local mock when the
Shell isn't configured.

Data layer (new)

src/lib/leads-api.ts — crm.lead.search/get/stats/create/update/
updateStatus/assign/sendForVerification + media (presign upload/download)
src/lib/verify-api.ts — crm.leadVerification.search/get/stats/verify/
markUnverified/assign/reassign/moveToPending

Backend → FE wiring

Assignee / creator names: read the resolved DTO fields and, as a safety
net, resolve member ids → real names against crm.team.member.search
(be-crm currently echoes the raw principalId as the name).
Created By: read the createdBy object the backend returns (was blank).
Site photos: upload via crm.media.presignUpload → PUT, persist through
crm.lead.attachment.add (per photo, after create), render in the detail
popup via crm.media.presignDownload.
Duplicate guard: surface the backend's real error (detail / duplicate_lead)
instead of the SDK's opaque "data command failed: 400".

UX

Leads detail: Property Photos gallery + edit-mode photo add/remove.
Verification: "Change Assignee" now opens a searchable, scrollable popup
instead of a long inline dropdown.
Removed the static "Storm Zone" tag from lead cards/detail; storm banner
only renders when the lead carries storm data.

Reference / follow-ups

leads.http, leads.postman_collection.json — be-crm data-door requests.

Integrates the Leads and Lead Verification screens with the live be-crm backend (crm.lead.* / crm.leadVerification.* / crm.media.*) behind a mode-agnostic data layer that still falls back to the local mock when the Shell isn't configured. Data layer (new) - src/lib/leads-api.ts — crm.lead.search/get/stats/create/update/ updateStatus/assign/sendForVerification + media (presign upload/download) - src/lib/verify-api.ts — crm.leadVerification.search/get/stats/verify/ markUnverified/assign/reassign/moveToPending Backend → FE wiring - Assignee / creator names: read the resolved DTO fields and, as a safety net, resolve member ids → real names against crm.team.member.search (be-crm currently echoes the raw principalId as the name). - Created By: read the createdBy object the backend returns (was blank). - Site photos: upload via crm.media.presignUpload → PUT, persist through crm.lead.attachment.add (per photo, after create), render in the detail popup via crm.media.presignDownload. - Duplicate guard: surface the backend's real error (detail / duplicate_lead) instead of the SDK's opaque "data command failed: 400". UX - Leads detail: Property Photos gallery + edit-mode photo add/remove. - Verification: "Change Assignee" now opens a searchable, scrollable popup instead of a long inline dropdown. - Removed the static "Storm Zone" tag from lead cards/detail; storm banner only renders when the lead carries storm data. Reference / follow-ups - leads.http, leads.postman_collection.json — be-crm data-door requests.

Mayur7887 added 1 commit 2026-07-24 09:55:59 +00:00

feat(leads+verification): wire Leads & Lead Verification to be-crm data door fd2e02086e

Integrates the Leads and Lead Verification screens with the live be-crm
backend (crm.lead.* / crm.leadVerification.* / crm.media.*) behind a
mode-agnostic data layer that still falls back to the local mock when the
Shell isn't configured.

Data layer (new)
- src/lib/leads-api.ts    — crm.lead.search/get/stats/create/update/
  updateStatus/assign/sendForVerification + media (presign upload/download)
- src/lib/verify-api.ts   — crm.leadVerification.search/get/stats/verify/
  markUnverified/assign/reassign/moveToPending

Backend → FE wiring
- Assignee / creator names: read the resolved DTO fields and, as a safety
  net, resolve member ids → real names against crm.team.member.search
  (be-crm currently echoes the raw principalId as the name).
- Created By: read the createdBy object the backend returns (was blank).
- Site photos: upload via crm.media.presignUpload → PUT, persist through
  crm.lead.attachment.add (per photo, after create), render in the detail
  popup via crm.media.presignDownload.
- Duplicate guard: surface the backend's real error (detail / duplicate_lead)
  instead of the SDK's opaque "data command failed: 400".

UX
- Leads detail: Property Photos gallery + edit-mode photo add/remove.
- Verification: "Change Assignee" now opens a searchable, scrollable popup
  instead of a long inline dropdown.
- Removed the static "Storm Zone" tag from lead cards/detail; storm banner
  only renders when the lead carries storm data.

Reference / follow-ups
- leads.http, leads.postman_collection.json — be-crm data-door requests.
- LEADS_BACKEND_CHANGES.md — required be-crm changes (name resolution,
  assignee carry-over on sendForVerification) verified against :4010.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

tanweer919 merged commit 53b6a08d2e into goutamnextflow

2026-07-24 09:58:04 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Goutam/lynkeduppro-crm#35