Now the scheduler endpoint for /tasks allows for certain query parameters and a body payload to be used. This can lead to confusion when certain query parameters are duplicated within the request body. We can solve this in two ways:
All filtering should be done in the body payload
All filtering should be done with query parameters
From these two options, the second one seems the most straightforward one. This in part since it will adhere to API conventions of other services within OpenKAT. We do however need to decide upon how we would structure our queryparams especially when regarding complex queries.
Now the scheduler endpoint for
/tasksallows for certain query parameters and a body payload to be used. This can lead to confusion when certain query parameters are duplicated within the request body. We can solve this in two ways:From these two options, the second one seems the most straightforward one. This in part since it will adhere to API conventions of other services within OpenKAT. We do however need to decide upon how we would structure our queryparams especially when regarding complex queries.
Related: https://github.com/minvws/nl-kat-coordination/issues/3162