The endpoint GET /classifier-jobs/{id}/summary used to return values inside reviewStatus block that's based on the whole project. But because of the changes in #568 the behavior of reviewStatus response changed from returning counts across the whole job to return it based on the parameters given in the changes inside #568.
Goal
What the arbimon team is looking for in this change is to have another endpoint (the name is up to you guys) to retrieve the attributes inside reviewStatus across the whole project. Separated from the current GET /classifier-jobs/{id}/summary endpoint would be good. Because on the frontend (see image below). This new API will be used on the "Validation status" block, and the summary endpoint can solely be used for the bottom "Detections" section.
Description
The endpoint
GET /classifier-jobs/{id}/summary
used to return values insidereviewStatus
block that's based on the whole project. But because of the changes in #568 the behavior ofreviewStatus
response changed from returning counts across the whole job to return it based on the parameters given in the changes inside #568.Goal
What the arbimon team is looking for in this change is to have another endpoint (the name is up to you guys) to retrieve the attributes inside
reviewStatus
across the whole project. Separated from the currentGET /classifier-jobs/{id}/summary
endpoint would be good. Because on the frontend (see image below). This new API will be used on the "Validation status" block, and the summary endpoint can solely be used for the bottom "Detections" section.