You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Contest_API.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -531,7 +531,7 @@ Data is immutable though: only inserts, no updates or deletes of
531
531
objects. It does have associated timestamp/contest time property.
532
532
Inserts and deletes are notified via the event feed. **Note**:
533
533
judgements are the exception to immutability in a weak sense: they get
534
-
updated once with the final verdict.
534
+
updated once with the final verdict, and the value for `current` may change.
535
535
536
536
Aggregate data: Only `GET` makes sense. These are not included in the
537
537
event feed, also note that these should not be considered proper REST
@@ -1715,6 +1715,7 @@ Properties of judgement objects:
1715
1715
| submission\_id | ID | Identifier of the [submission](#submissions) judged.
1716
1716
| judgement\_type\_id | ID ? | The [verdict](#judgement-types) of this judgement. Required iff judgement has completed.
1717
1717
| score | number | Score for this judgement. Required iff contest:scoreboard\_type is `score`.
1718
+
| current | boolean ? | `true` if this is the current judgement. Defaults to `true`. At any time, there must be at most one judgement per submission for which this `true` or unset (and thus defaulting to `true`).
1718
1719
| start\_time | TIME | Absolute time when judgement started.
1719
1720
| start\_contest\_time | RELTIME | Contest relative time when judgement started.
1720
1721
| end\_time | TIME ? | Absolute time when judgement completed. Required iff judgement\_type\_id is present.
0 commit comments