Refactoring Dead Code
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 55/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- developer-experience
Research direction
Read the linked Sprint-3/3-dead-code coursework and inspect only that directory in the coursework repository. Identify the unused code described by the exercise, follow the repository’s demonstrated approach for handling dead code, and confirm the directory remains clean after the refactor.
Written by the indexing model from the issue text.
Description
Link to the coursework
https://github.com/CodeYourFuture/Module-Structuring-and-Testing-Data/tree/main/Sprint-3/3-dead-code
Learning Objectives
- Identify 'dead code' in an existing code base
- Demonstrate how we handle 'dead code' in our codebases
Why are we doing this?
The presence of "dead code" can impact the efficiency and developer experience of a code repository. Learning to refactor code to be clean and efficient will help you be a better developer and future-proof your code.
Maximum time in hours
1
How to get help
Share your blockers in your class channel
https://curriculum.codeyourfuture.io/guides/getting-help/asking-questions/
How to submit
- In your fork of the coursework repo, checkout the main branch
- Make a new branch from
maincalledcoursework/sprint-3-dead-code - Make regular small commits in this branch with clear messages.
- When you are ready, open a PR to the CYF repo, following the instructions in the PR template.
There are several directories in this repo. Make a new branch for each issue in each sprint. Only change files in the Sprint-3/3-dead-code directory.
Anything else?
No response
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 397
- PR merge metrics
- No merged PRs in 30d
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.
More from CodeYourFuture/Module-Structuring-and-Testing-Data
-
🏕 Priority Mandatory 📅 Sprint 1 Core Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
🏕 Priority Mandatory 📅 Sprint 3 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
:gear: bug 📅 Sprint 3 Module-Structuring-And-Testing-Data NotCoursework
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
🏕 Priority Mandatory 📅 Sprint 1 Core Module-Structuring-And-Testing-Data Submit:None 🦔 Size Tiny
Difficulty 1/5 Under an hour Newbie friendliness 35/100
-
🏝️ Priority Stretch 🐂 Size Medium 📅 Sprint 1 📅 Sprint 2 📅 Sprint 3 Module-Structuring-And-Testing-Data Optional Submit:None
Difficulty 1/5 Under an hour Newbie friendliness 45/100
All issues in CodeYourFuture/Module-Structuring-and-Testing-Data
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·