technicalpickles / technicalpickles/homesick
General refactoring
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.5k
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
I have started work on some of this on my refactor branch several of my branches. If you would like to work on the branch with me, let me know and I can accept PRs / add you as a collaborator.
Ideas
- Make rubocop happy with our source code.
- Separate implementation and specs into more files.
- Reduce duplication.
- Make things more modular
- Use more libraries to avoid "reinventing the wheel".
- Move each group of commands into their own/class file. For example, symlink/unsymlink could be together. We could also have spec files separated into these command groups.
Thanks to @trobrock for some of these refactoring ideas.
Related issues
- #62
- #74
- #75
Contributor guide
No contributing guide indexed for this repository
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 reviewing the refactor branches mentioned in the issue and the related issues #62, #74, and #75, then inspect the source and spec layout. The issue lists possible goals—Rubocop compliance, reduced duplication, modular commands, and separated specs—but does not define a bounded completion criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100