Bug 32942: Suggestion API route when non 'standard' status are present
authorFrédéric Demians <f.demians@tamil.fr>
Fri, 10 Feb 2023 17:23:11 +0000 (18:23 +0100)
committerFridolin Somers <fridolin.somers@biblibre.com>
Thu, 21 Sep 2023 06:01:17 +0000 (20:01 -1000)
commit745a6bde5e58bda0ba4eb619dcf2253ab63da5df
treee1c4252b4ea603fa0bbb0bcb80ae42bbabe25b3a
parent585a816aff11fbfdcc9637bcc96f09c82d3a34a3
Bug 32942: Suggestion API route when non 'standard' status are present

The API route for listing all suggestion:

/api/v1/suggestions

send back an error message when there is a suugestion with non standard
status (ASKED, CHECKED, ACCEPTED, REJECTED).

This patch fixes this too restrictive restriction.

TO TEST:

1. Add a status in SUGGEST_STATUS AV list.
2. Create a suggestion, and assign it to the previsous status.
3. Call /api/v1/suggestion
3. You get an error message:
   {
    "errors": [ {
      "message":"Not in enum list: ASKED, CHECKED, ACCEPTED, REJECTED.",
      "path":"\/1\/status"
    }],
    "status":200
   }
4. Apply the patch. Call /api/v1/suggestion

Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
Signed-off-by: Martin Renvoize <martin.renvoize@ptfs-europe.com>
Signed-off-by: Tomas Cohen Arazi <tomascohen@theke.io>
(cherry picked from commit 3dc9bf900bd666eb17272060e071422a35267ada)
Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com>
api/v1/swagger/definitions/suggestion.yaml