Remove unused code and obsolete components #97
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mainadapter
force-pushed
the
refactor/remove-unused-code
branch
from
d639dbe to
7abefac
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧹 Summary
This PR focuses on cleaning up unused code across the project to enhance maintainability, clarity, and performance. It removes unnecessary imports, variables, components, and redundant logic that were no longer in use.
✨ Changes Overview
Removed unused components:
Carousel.tsxLogo.tsxand its references, as it always returnednullCleaned up imports:
Footer,Header,Navigation,HeroCall,RepoLanguages,Rules, etc.)Pruned obsolete props and variables:
diferentColor,imageUrl, andisDesktopSimplified forms and pages:
PersonalDataForm,MinhaÁrea,Regras, and related components🎯 Purpose
Improve overall code clarity and maintainability by removing dead code, reducing bundle size, and making the codebase easier to navigate and maintain.
🚧 Next Steps
There are still some TypeScript type errors in the codebase, particularly related to the use of the any type.
These were not addressed in this PR to keep the scope focused. It’s recommended to create a dedicated PR to handle type improvements and strengthen type safety across the project.