cms-dev
Make subtask numbering/naming more flexible
https://github.com/ioi-2024/cms/commit/f918b0f09fbe1a584eae4689e8d43ec36937c329
i can't tell at a glance, but if this is (on the user's side) only relevant for the section headings in cws / column names in rws, then maybe it'd make sense to generalize this to allow specifying custom names for subtasks. once you get to tasks with 6 or 7 subtasks, referring to them by the actual constraints is more clear than just a number, in my opinion.
I don't think we want to expose subtask names to contestants; or at least, it's a bigger change that probably needs some discussion with (I)SC for IOI.
Zero-based subtask numbers we should OTOH do.
What about presenting the subtask as "Sample subtask" instead of "Subtask 0"?
What about presenting the subtask as "Sample subtask" instead of "Subtask 0"?
That seems reasonable enough to me.
What about presenting the subtask as "Sample subtask" instead of "Subtask 0"?
In that case i think it should be made toggleable somewhere. i wouldn't want to assume that every task always has a sample subtask.
re: named subtasks:
I don't think we want to expose subtask names to contestants; or at least, it's a bigger change that probably needs some discussion with (I)SC for IOI.
i don't see how this exposes new information. If ISC wants they can just name their subtasks the strings "subtask 1", "subtask 2", etc.
IMO that's sort of implied by numbering the subtask "0"...
Given the nontrivial amount of design choices, I propose we start by doing what IOI did, and then discuss on how to make this more flexible.
oh, i might have been unclear. i would like there to be a toggle for whether subtask 0 (or "sample subtask") exists or not. when false, numbering should still start from 1. in some cases (output-only tasks come to mind), having sample inputs that are graded does not make sense.