Closed thorehusfeldt closed 1 year ago
See d6731f00163e0274f6b926cc79ffb9d303362ab7 (numbering
branch).
Made it so that unlisted testdata.yaml
always error and are removed on --clean
. An empty testdata.yaml:
key currently just implies the absense of such a file.
I'd prefer to not yet add any specific handling for now -- this can be done when it's needed.
Currently, the generators script is lenient about existing
testdata.yaml
files indata
. It notes their existence with a yellow warningbut otherwise leaves them alone.
Since
testdata.yaml
critically modifies the behaviour of input validation (and potentially grading), I think we should be more strict and require these files to be explicitly listed in thegenerators.yaml
and otherwise removed. At least the tool should be as prissy as with unlisted testcases and in angry red complain something similar toTrying to think of a situation where I’d want unlisted
testdata.yaml
floating around in thedata
directory: Maybe somebody writes a tool that auto-generatestestdata.yaml
. Then at least I’d expectin
generators.yaml
to signal explicitly that the file exists. That’s still too implicit for my taste, so I’d prefer something like