*_has_changed logic is now useless
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 412
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 3
Description
Is there any reason to keep the {whatever}_has_changed logic in the loaders? We initially added it because we wanted to support loading only a subset of the tasks in a given contest, but now we can import tasks one-by-one: it seems to me that now it may cause more issues than those it solves (ie. none).
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 loaders and the {whatever}_has_changed logic referenced in the issue. Read how task imports are now performed one by one and check any nearby coverage before removing the obsolete subset-loading behavior. Done means the loaders no longer depend on this logic and individual task imports still work as intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100