Make subtask numbering/naming more flexible
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
https://github.com/ioi-2024/cms/commit/f918b0f09fbe1a584eae4689e8d43ec36937c329
i can't tell at a glance, but if this is (on the user's side) only relevant for the section headings in cws / column names in rws, then maybe it'd make sense to generalize this to allow specifying custom names for subtasks. once you get to tasks with 6 or 7 subtasks, referring to them by the actual constraints is more clear than just a number, in my opinion.
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 reading commit f918b0f09fbe1a584eae4689e8d43ec36937c329 and locating how cws section headings and rws column names currently represent subtasks. Clarify whether both views are in scope, then define the expected custom-name behavior and verify that those names appear consistently instead of fixed numbering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100