Allow configuring the filename format for OutputOnly tasks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the OutputOnly task type and the USER_OUTPUT_FILENAME_TEMPLATE constant, then trace how task parameters are defined and consumed. The work is done when the filename template can be configured for an OutputOnly task while retaining the current default naming behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100