Open maxgraziano opened 6 months ago
Fetching the proposal directly (ex: /coops/proposal/782
using example above), returns the linked coop record (see coop = 780 below). This shows the issue is not due to model relationships or object linking, but an issue with the fetch of the data.
{
"id": 782,
"proposal_status": "PENDING",
"operation": "UPDATE",
"change_summary": "{\"coop_public_id\": 4, \"requested_by\": \"chicommons\", \"proposal_status\": \"PENDING\", \"operation\": \"UPDATE\", \"requested_datetime\": \"2024-05-15 15:05:33.756841+00:00\"}",
"review_notes": null,
"coop_public": 4,
"requested_by": 1,
"requested_datetime": "2024-05-15T10:05:33.756841-05:00",
"reviewed_by": null,
"reviewed_datetime": null,
"coop": 780
}
Reported by @domdelorenzo, Verified by @maxgraziano
Steps to reproduce: In development environment, using preloaded dataset.
1) Authenticate as admin user.
2) Create an UPDATE proposal record via POST to the
/coops/proposal/create/
endpoint.3) Confirm you get a
201
HTTP response. Take note of the proposal ID returned (782 in the example below).4) Make
GET
request to/coops/unapproved
endpoint. Confirm200
HTTP response. Find record with ID from step 3.Expected Behavior:
/coops/unapproved/
should not be returning null values. Values should be the same as public coop 4, but with the name field changed per proposal.