Everything is a method, but I don't think it should be like this
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
I'm getting a bit too much into refactoring now, but it feels hard to progress otherwise.
For the most part, there are no subs at all, even if something does not need to do anything with the object it's being called on. Because of that a lot of stuff has to be like self.get-short-commit instead of just get-short-commit. I think we can do better.
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
Search the bot code for calls such as self.get-short-commit and inspect the surrounding method and sub definitions. Determine which operations genuinely need an object, then document the intended scope and acceptance criteria before changing the call structure; the issue names no files, tests, or concrete completion check.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100