api: apply consistent behaviour of the reverse query parameter (#12244)

This commit is contained in:
Luiz Aoqui
2022-03-11 19:44:52 -05:00
committed by GitHub
parent 4a21dbcfaa
commit ddbbda6561
13 changed files with 321 additions and 189 deletions

View File

@@ -57,9 +57,10 @@ The table below shows this endpoint's support for
Specifying `*` will return all evaluations across all authorized namespaces.
This parameter is used before any `filter` expression is applied.
- `ascending` `(bool: false)` - Specifies the list of returned evaluations should
be sorted in chronological order (oldest evaluations first). By default evaluations
are returned sorted in reverse chronological order (newest evaluations first).
- `reverse` `(bool: false)` - Specifies the list of returned evaluations should
be sorted in the reverse order. By default evaluations are returned sorted in
chronological order (older evaluations first), or in lexicographical order by
their ID if the `prefix` query parameter is used.
### Sample Request