Skip to content

Enrich PartnerSuggestion serializer with incident card fields#57

Merged
immerSIR merged 1 commit into
223MapAction:mainfrom
immerSIR:fix/suggestion-card-incident-fields
Jul 2, 2026
Merged

Enrich PartnerSuggestion serializer with incident card fields#57
immerSIR merged 1 commit into
223MapAction:mainfrom
immerSIR:fix/suggestion-card-incident-fields

Conversation

@immerSIR

@immerSIR immerSIR commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Problem

In the frontend Collaborations → Demandes tab, cards sourced from partner suggestions (/my-suggestions/received/, /my-suggestions/sent/) rendered empty — no photo, no description, no incident details — while cards sourced from collaboration requests (/collaboration/) rendered fully. The two lists are merged in the same tab, so the suggestion cards looked broken.

Root cause

PartnerSuggestionSerializer exposed only incident_title, whereas CollaborationSerializer also exposes incident_photo, incident_thumbnail, incident_details, etc. The FE renders both card types with the same component, so suggestion items had nothing to show.

Fix

Add to PartnerSuggestionSerializer the same incident card fields as CollaborationSerializer (all read-only, additive — no breaking change):
incident_photo, incident_thumbnail, incident_description, incident_zone, incident_etat, incident_details.

Verified on prod: the incident data + storage files (photo/thumbnail) already resolve (HTTP 200); only the serializer was missing the fields.

Docs updated in Dashboardv2/BACKEND_API.md (+ .fr.md).

@immerSIR immerSIR force-pushed the fix/suggestion-card-incident-fields branch from 6ffc3a7 to 9a8ceba Compare July 2, 2026 01:00
@immerSIR immerSIR merged commit 3da8c3a into 223MapAction:main Jul 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant