Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow configuring the filename format for OutputOnly tasks #1194

Open
SvizelPritula opened this issue Sep 20, 2021 · 2 comments
Open

Allow configuring the filename format for OutputOnly tasks #1194

SvizelPritula opened this issue Sep 20, 2021 · 2 comments

Comments

@SvizelPritula
Copy link
Contributor

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.

@fushar
Copy link
Contributor

fushar commented Sep 3, 2022

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)

@SvizelPritula
Copy link
Contributor Author

I've acually implemented this in https://github.com/SvizelPritula/cms/tree/output-filename, but thats based on the IOI 2022 CMS version and since I already have 2 PR in this repo and I'm a bit lost in all my git branches.

@wil93 wil93 added this to the P1 milestone Nov 27, 2022
@wil93 wil93 added the pr_ready label Nov 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants