-
Notifications
You must be signed in to change notification settings - Fork 243
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
improve code quality #17
Comments
Hello, It's actually a great idea, if we want to focus on rewriting things, we may also write a cleaner code, with self-documentation. I believe it's a great idea to use perlpod too. despite we must have a release for tomorrow #19, let's just fix simple issues for release @rezasp please review and let us know if you agree. Best Regards. |
Hello, Thank you for sharing us your great idea, I agree, I am working on a few enhancements for tomorrow, and let you know when I'm finished. Regards. |
ok. Great. I will refactor the code. When I'm done I will send a PR. |
Hey, thanks for updating us. be in touch (Y). regards. |
I have sent a PR.
I resisted the urge to fix/cleanup more. |
Hello @StPanning, Thanks for your contribution, I will review your code after BH Arsenal Singapore. the details you shared is very useful. Best Regards. |
The current code is written in a way that makes it hard to contribute:
To make the code easier to maintain I suggest that:
use warnings
anduse strict
everywhere.
package
As a first step I would:
modules/
in a separate namespace, likeJoomScan/Check
I would only change the code that needs to be changed to make the code work,
to keep the extensive changes to a minimum.
after this is done, I would proceed with the rest of the code.
some example:
modules/robots.pl orig:
would become JoomScan/Check/RobotsTXT.pm:
I think that code could still be improved, but I would leave that for the next round of refactoring
The text was updated successfully, but these errors were encountered: