Rename Overlord task "shutdown" to "cancel"
Open
Refactoring
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 58m
- Merged PRs (30d)
- 233
Description
It seems to be an unfortunate name because "shutdown" sounds like a type of task itself, not a task cancellation request.
For retaining backward compatibility, old endpoints should still be supported (with a warning logged issued when they are called), but generally, it should be called "canceled" in new endpoints and throughout the documentation, codebase, and new HTTP endpoints.
Contributor guide
Research direction
Start by locating the Overlord task "shutdown" endpoints and all related references in the codebase and documentation. Update new HTTP endpoints and documentation to use "cancel" or "canceled", while keeping old endpoints supported with a logged warning when called.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, documentation
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100