-
Notifications
You must be signed in to change notification settings - Fork 74
Oonirun v2.1 #301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oonirun v2.1 #301
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me this is good to go. Once @LDiazN marks it as approved, we can merge it. 🐳
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved!
WIP specification update for OONI Run v2.1
implements ooni/backend#930