Judge capabilities #145
Judge capabilities #145
Conversation
Contest_API.md
Outdated
| All requests must include a valid JSON object with the same properties as the commentary | ||
| endpoint returns from a `GET` request with the following exceptions: | ||
|
|
||
| - The `judge\_comment` capability only has access to `POST`. `id`, `time`, |
There was a problem hiding this comment.
Nitpick: since no PUT is defined, this is not really necessary. But I'm fine with leaving it in, for in case we add that.
There was a problem hiding this comment.
This was copied from similar capabilities, will try to improve as part of a rewrite.
team_clar has been changed to a generic post_clar, and a post_comment capability with access equivalent to what a judge/analyst should be able to do has been added, and described similar to other capabilities.
| All requests must include a valid JSON object with the same properties as the commentary | ||
| endpoint returns from a `GET` request with the following exceptions: | ||
|
|
||
| - The `post\_comment` capability only has access to `POST`. `id`, `time`, |
There was a problem hiding this comment.
I think this first sentence should be removed. In the clarifications endpoint it made sense since there was also a {proxy,admin}_clar capability with PUT access, but here there is only POST.
| - The `post\_comment` capability only has access to `POST`. `id`, `time`, | |
| - `id`, `time`, |
Co-authored-by: Jaap Eldering <[email protected]>
|
@deboer-tim What is the status of this? Can we close? |
|
Discuss on the next call? This is implemented on the CDS and is required API support for clients to submit commentary - but I'm not aware of anyone else looking at / implementing this so not sure if it's worth spec or should just be a CDS-specific extension for now. |
Edited:
team_clar has been changed to a generic post_clar, and a post_comment capability with access equivalent to what a judge/analyst should be able to do has been added, and described similar to other capabilities.