1709 send feedbacks in report processes updates
Created by: Tirokk
Authored by roschaefer Closed
🍰 Pullrequest
@Tirokk here are some proposed changes. @mattwr18 and I finally went the way to implement an extra resolver and a dedicated UI for the list of reported content. The turning point was when we wrote GraphQL statements manually and could see a long list of special cases that we would have to check if we expose graphlQL tye Report
to any authenticated user. E.g. we would have to check that you cannot access FILED
(or just one record) that submitter
of FILED
would not return undefined
, etc.
So the suggestion is that we roughly implement this diagram:
If you are the author of a reported content you will get a notification that points to a resource not a report. If you yourself have been blocked, you would see an error message on login.