Freegle / Iznik / 27048

72%

master: 72%

Pull #1066

circleci

fix(message): re-derive locationid from lat/lng on PATCH so TN postcode edits stick

PATCH /message (and /message/tn/:tnpostid) applied req.Lat/req.Lng to messages.lat/lng
but never touched messages.locationid. Both the subject-line reconstruction
(constructLocationString) and the owner/mod-facing location display always prefer
locationid over raw lat/lng, so a TN edit that only supplies corrected coordinates left
the postcode pinned to whatever locationid was set before the edit - appearing to
"revert" and staying stuck no matter how many times the coordinates were corrected
(Discourse 9908).

resolvePatchLocationID keeps locationid in sync with lat/lng when the caller (partner
integrations like Trash Nothing, which have no concept of Freegle location IDs) supplies
coordinates without an explicit locationid, using the same nearest-postcode lookup
already used by the read path and TN mail ingestion. An explicit locationid still wins.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

13006 of 17141 branches covered (75.88%)

Branch coverage included in aggregate %.

14 of 14 new or added lines in 1 file covered. (100.0%)

136206 of 189241 relevant lines covered (71.97%)

37.76 hits per line