Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code Refactored for readability and maintainability #1304

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

piyushjoshi01
Copy link

Improved Code Quality by removing code smells like Complex Conditional, Complex Method, Cyclically-dependent Modularization, Insufficient Modularization.

@piyushjoshi01
Copy link
Author

piyushjoshi01 commented Mar 31, 2024 via email

Copy link
Member

@mwithi mwithi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @piyushjoshi01, thank you for your effort and contribution to this project. Upon reviewing it, we've identified a few concerns that need to be addressed before we can proceed with merging.

Firstly, there seem to be conflicts with existing files as indicated in the "PR automatic review" below. Additionally, we've noticed that there are some discrepancies between the test frameworks being used (Junit 4 versus Junit 5) which need to be rectified for consistency within our project standards.

Furthermore, while we appreciate the effort in refactoring the code into smaller methods, it appears that some of these methods lack comprehensive JavaDoc documentation. Additionally, we are concerned that the refactoring may introduce unnecessary overhead in terms of runtime due to increased method calls.

We truly value your contributions and believe that with these adjustments, your changes could significantly enhance our codebase. We encourage you to address these points and to have a look to the Code Style requsitions.

@piyushjoshi01
Copy link
Author

piyushjoshi01 commented Apr 3, 2024 via email

@mwithi mwithi added the hold hold for next releases label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hold hold for next releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants