Skip to content

Commit 9a87f1f

Browse files
committed
Specify explicitly that nullable IDs can be filtered on
Also explicitly mention that filtering only needs to be supported on properties listed in the access endpoint. Adresses the "on a related note" in #193 (comment)
1 parent 935dc88 commit 9a87f1f

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

Contest_API.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -597,9 +597,10 @@ Note that all results returned from endpoints:
597597
### Filtering
598598

599599
Endpoints that return a JSON array must allow filtering on any
600-
property with type ID (except the `id` property) by passing it as a
601-
query argument. For example, clarifications can be filtered on the sender
602-
by passing `from_team_id=X`. To filter on a `null` value,
600+
property specified in the [Access](#access) endpoint with type `ID` or
601+
`ID ?` (except the `id` property) by passing it as a query argument.
602+
For example, clarifications can be filtered on the
603+
sender by passing `from_team_id=X`. To filter on a `null` value,
603604
pass an empty string, i.e. `from_team_id=`. It must be possible to
604605
filter on multiple different properties simultaneously, with the
605606
meaning that all conditions must be met (they are logically `AND`ed).

0 commit comments

Comments
 (0)