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
Is your feature request related to a problem? Please describe.
The OutputOnly task type requires files named output_*code*.txt, but some organisers use different naming conventions, like *code*.out.
Describe the solution you'd like
A text parameter could be added to the OutputOnly task type to replace the existing USER_OUTPUT_FILENAME_TEMPLATE constant.
Describe alternatives you've considered
The ioi2022 fork simply changes the constant to their preferred format, but this could easily be configurable instead of requiring changing the source code.
Additional context
I don't have too much experience with contributing to free software projects, but I could try to implement this once I get a development VM running, since this seems an easy change.
The text was updated successfully, but these errors were encountered:
As a reference, for IOI 2022 we hardcode the filename format in this commit: ioi@eae340e (Output-only: Change output filename extension from .txt to .out)
Is your feature request related to a problem? Please describe.
The OutputOnly task type requires files named
output_*code*.txt
, but some organisers use different naming conventions, like*code*.out
.Describe the solution you'd like
A text parameter could be added to the OutputOnly task type to replace the existing
USER_OUTPUT_FILENAME_TEMPLATE
constant.Describe alternatives you've considered
The ioi2022 fork simply changes the constant to their preferred format, but this could easily be configurable instead of requiring changing the source code.
Additional context
I don't have too much experience with contributing to free software projects, but I could try to implement this once I get a development VM running, since this seems an easy change.
The text was updated successfully, but these errors were encountered: