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
We need an efficient way to specify testcases in a common format for a contest, where dynamic keys are not an optimal solution. For example, the regex \w+\.(?<batch>[0-9]+)-(?<case>[0-9]+)\.in matches most, if not all, COCI data.
That's a lot of data.
That's a lot of lines of init.yml saved.
There are probably more broad ways to approach this, but for the general case a simple regex would save a lot of work, even if it loses flexibility for more complex cases (dynamic keys are there for those!)
Someday this may be generalized to support setting a format specifier for a specific test_cases node, but that is beyond the scope of this ticket. For this ticket, if test_format_(in|out) exists, then the test_cases node should be ignored.
The text was updated successfully, but these errors were encountered:
We need an efficient way to specify testcases in a common format for a contest, where dynamic keys are not an optimal solution. For example, the regex
\w+\.(?<batch>[0-9]+)-(?<case>[0-9]+)\.in
matches most, if not all, COCI data.That's a lot of data.
That's a lot of lines of
init.yml
saved.There are probably more broad ways to approach this, but for the general case a simple regex would save a lot of work, even if it loses flexibility for more complex cases (dynamic keys are there for those!)
The following should be valid, after this ticket:
Someday this may be generalized to support setting a format specifier for a specific
test_cases
node, but that is beyond the scope of this ticket. For this ticket, iftest_format_(in|out)
exists, then thetest_cases
node should be ignored.The text was updated successfully, but these errors were encountered: