Conversation
Question: do we want to use headers for this or should we instead make a new post handler which does these in the request body? That would be slightly more flexible if we would like to use this request to pass additional data as part of the first request.
sdsantos
left a comment
sdsantos
left a comment
There was a problem hiding this comment.
This look to be breaking changes to the schema. Should the endpoints become .../api/v2.1/...?
The concern here is that |
Fix syntax of targets
|
I think I have come up with a better solution to handle older clients in: 6f70178. Basically we don't need to have a new key, but instead we just handle extra metadata for inputs through It also should make the implementation easier and not have to handle multiple different cases depending on client support. |
* Drop targets and replace with `inputs_extra` * Cleanup some text
- Move fields from headers to body - Move fields from query parameters to body - Mark fields for dynamic test lists calculation as required
4 participants
WIP specification update for OONI Run v2.1
implements ooni/backend#930