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 commit3dc9bf900b
) Signed-off-by: Fridolin Somers <fridolin.somers@biblibre.com> (cherry picked from commit745a6bde5e
) Signed-off-by: Matt Blenkinsop <matt.blenkinsop@ptfs-europe.com>
This commit is contained in:
parent
295497b557
commit
6acfa90cc7
1 changed files with 0 additions and 5 deletions
|
@ -65,11 +65,6 @@ properties:
|
|||
status:
|
||||
type: string
|
||||
description: Suggestion status
|
||||
enum:
|
||||
- ASKED
|
||||
- CHECKED
|
||||
- ACCEPTED
|
||||
- REJECTED
|
||||
note:
|
||||
type:
|
||||
- string
|
||||
|
|
Loading…
Reference in a new issue