Refactor: Rename interfaces to use "I" prefix and extract Component Props into separate interfaces #36
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.
This pull request proposes renaming all interfaces in the codebase to start with an "I" (e.g., User to IUser). This change follows the widely adopted convention of prefixing interfaces with "I" to clearly distinguish them from classes and regular objects. Adhering to this practice helps improve the readability and clarity of the code, especially when the code is being worked on or reviewed by various contributors.
Additionally, several React component props have been refactored into separate interfaces. This change enhances the maintainability and scalability of the code by making it more modular. Each component now has a clearly defined structure for its props, which also facilitates easier refactoring and reuse of components.
I hope these changes help improve the codebase and I’m happy to discuss further or make adjustments based on feedback.
Reasons for the Change:
Clarity and Consistency: Renaming interfaces with the "I" prefix follows a well-established convention, making it easier for contributors to quickly recognize interfaces in the codebase.
Improved Maintainability: Moving props into separate interfaces improves the modularity and structure of the code, enabling safer changes and easier reusability of components.
Better Readability: The code becomes more understandable by clearly separating interface definitions from their implementations.
Changes:
stroke-width
attribute in react components