This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
Implement MSC2414: Make reason and score parameters optional for reporting content #8551
Labels
A-Spec-Compliance
places where synapse does not conform to the spec
good first issue
Good for newcomers
T-Enhancement
New features, changes in functionality, improvements in performance, or user-facing enhancements.
MSC2414 made the
reason
andscore
parameters for the POST /_matrix/client/r0/rooms/{roomId}/report/{eventId} endpoint.That endpoint is implemented in Synapse here:
synapse/synapse/rest/client/v2_alpha/report_event.py
Lines 31 to 46 in 8a4a418
The Event Reports Admin API should also be updated to state that the
reason
andcontent
fields may be both blank andnull
, and the Admin API endpoint should be updated to expectNone
values for these keys as well:synapse/synapse/storage/databases/main/room.py
Lines 1388 to 1389 in cbabb31
(that function may not actually need updating, but it would be good to check that the API still behaves as expected).
Some tests for clients sending reports without
reason
andscore
would be great as well.This will need to be implemented in order to eventually advertise support for the next Client-Server API version.
The text was updated successfully, but these errors were encountered: