Giuliano1993 / Giuliano1993/make-js-component
Code refactor
- Dominant language
- JavaScript
- Stars
- 40
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I have already contributed to the project by implementing the React CSS Module feature.
I am excited about the project and really like it, but to be honest, I found the code to be somewhat procedural and, at times, repetitive and confusing.
For example, there are too many nested if/else statements, or repeated code between JS/TS in React components, and there are no comments in the code.
If you agree, I already have ideas on how to make it more extensible and open to modifications.
I believe this choice will completely influence the architecture of the library, so it would be appropriate to suspend the implementation of new features until the refactoring is done.
I also think that now is the right time, especially since the project is still small and there is no documentation yet.
I can put my ideas into action quickly, but with one condition: I am not very confident with TypeScript, so I would only handle the JavaScript part.
What do you think?
Contributor guide
Research direction
No files, tests, or entry points are named. Start by mapping the JavaScript and TypeScript React component structure and turning the broad architectural concerns into a bounded plan. Done would require an agreed refactoring scope and a reviewed implementation, but the issue does not define either.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, typescript
- Domain
- frontend, web-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100