🚀 Refactor: Code Modularisation
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by reviewing follow-up PR #7 and its footer component, since the issue provides no specific files, tests, or entry points. Before proceeding, agree on the component scope and checklist; done would require an approved plan covering the targeted files rather than this broad refactoring proposal.
Written by the indexing model from the issue text.
Description
🔖 Feature description
This issue suggests a refactoring effort aimed at improving the codebase by breaking it down into smaller components.
Note: I'm using the issue template for feature requests since there's no template for refactoring and also because this is neither a bug nor a documentation fix.
🎤 Pitch
By breaking down the code into smaller and more manageable components, we can enhance the readability and maintainability of the codebase. This refactor will not only make the code more approachable for new contributors but also improve the overall understanding and navigation of the project. It will also lead to optimisation since we can reuse these small components at multiple places.
For example: we can break down most of the component files into smaller components. I've created a follow up PR(#7) for the footer component. If it gets approved, we can probably create a common issue that covers file-by-file refactoring of multiple files using a check list.
PS: I'd like to work on this and follow up issue(s).
👀 Have you spent some time to check if this issue has been raised before?
- I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
- I have read the Code of Conduct
- Dominant language
- TypeScript
- Stars
- 45
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
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 appwrite/builtwith
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
🚀 Feature: Update project detailsMay be free again @joeyouss claimed this 1200 days ago, and no pull request is open. Openenhancement
appwrite/builtwith#25 · 3 comments · 1 reaction · 1 assignee ·
All issues in appwrite/builtwith
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
melgarafael/DeskcommCRM#1812 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
prisma/prisma-cli#309 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gregwebs/pi-quota-dispatcher#26 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openwatersio/slackwater.xyz#124 ·
Maintainers usually reply within 1 day
-
agent-reported area/browser area/docs documentation good first issue hacktoberfest help wanted P2
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 2 days