spinframework / spinframework/spin-operator
Rename ActiveScheduler to ActiveExecutor
Open
Nobody has claimed this yet.
api-next
- Dominant language
- Go
- Stars
- 289
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
The SpinApp status subresource has a field ActiveScheduler. It would be more aptly named ActiveExecutor because it refers to executors and then we're not mixing up nomenclature.
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
Inspect the SpinApp status subresource definition and search for all references to ActiveScheduler. Rename the field to ActiveExecutor consistently, then verify the operator's API and status behavior; the issue names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100