Closed AWegnerGitHub closed 7 years ago
Gonna take this one. Shouldn't be much more than moving an existing route to use a jbuilder view and a join. Possibly a day or two before I can work on it, though.
Gonna have to drop this one again - unexpected things came up, and I'm gone for a few days to sort them out. Will get round to it when I get back, if @Undo1 doesn't want it.
Currently FDSC does this by making a second request to the /api/post/:id/feedback
route, then counting the number of feedbacks of each type. You could use that approach in the meantime until Art gets a chance to fix it.
Although, it would be much more efficient (both time and network wise) to include this in the original request.
@ArtOfCode- any updates on the status of this?
When a post receives feedback from multiple users, it'd be helpful to know how many of each type (
is_fp
,is_tp
, andis_naa
) were received.For example, post https://metasmoke.erwaysoftware.com/post/44634 received 2
is_tp
and 1is_naa
and has a response object that looks like this:If there could be three new attributes showing the count of each, that'd be helpful. Example:
An alternative to adding three new attributes, is changing the existing (and new)
is_*
attributes from a boolean to an integer.