The way that the query gets built is super inconsistent internally, and needs a proper refactor. For now this just creates a deletion-specific view at the same time as the regular view so that it goes through the same logic.
Test plan
Tested against the test site with e.g. http://localhost:5000/status/feed?id=2004 and http://localhost:5000/status/?id=1133 (which failed before)
Summary
Fix #574
Detailed description
The way that the query gets built is super inconsistent internally, and needs a proper refactor. For now this just creates a deletion-specific view at the same time as the regular view so that it goes through the same logic.
Test plan
Tested against the test site with e.g.
http://localhost:5000/status/feed?id=2004andhttp://localhost:5000/status/?id=1133(which failed before)