-
Notifications
You must be signed in to change notification settings - Fork 201
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
Improved code style and fixed typos #1157
Improved code style and fixed typos #1157
Conversation
To ensure consistent code formatting, we use Black and isort. To auto-format the code, run the Add a Developer Certificate of Origin (DCO) to your commit. This certifies that you have the right to submit the code under an open-source license. How to write good commit messages? Refer to this guide: https://aboutcode.readthedocs.io/en/latest/contributing/writing_good_commit_messages.html |
84543f2
to
55f9adc
Compare
Signed-off-by: Michael Ehab <[email protected]>
Signed-off-by: Michael Ehab <[email protected]>
Signed-off-by: Michael Ehab <[email protected]>
Signed-off-by: Michael Ehab <[email protected]>
Signed-off-by: Michael Ehab <[email protected]>
Signed-off-by: Michael Ehab <[email protected]>
Signed-off-by: Michael Ehab <[email protected]>
Signed-off-by: Michael Ehab <[email protected]>
To ensure consistent code formatting, I used Black and isort to format the changed files. Signed-off-by: Michael Ehab <[email protected]>
Fixed more typos and formated the files Signed-off-by: Michael Ehab <[email protected]>
55f9adc
to
376ba41
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @michaelehab
Use consistent format for docstring see comments below
…tone Changed the doctrings to have a consistent format and used Black and isort to format the changed files. Signed-off-by: Michael Ehab <[email protected]>
@keshav-space please review when you get chance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @michaelehab
See the few suggestions below, and also need to resolve the conflicts before we can merge this.
Signed-off-by: Keshav Priyadarshi <[email protected]>
Signed-off-by: Keshav Priyadarshi <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @michaelehab
I have reverted some undesirable refactoring.
* style: modified snyk datasource file to follow pep 8 Signed-off-by: Michael Ehab <[email protected]> * style: modified osv datasource file to follow pep 8 Signed-off-by: Michael Ehab <[email protected]> * style: modified oss datasource file to follow pep 8 Signed-off-by: Michael Ehab <[email protected]> * style: modified vulnerablecode datasource file to follow pep 8 Signed-off-by: Michael Ehab <[email protected]> * style: modified gitlab datasource file to follow pep 8 Signed-off-by: Michael Ehab <[email protected]> * style: modified gitlab datasource file to follow pep 8 Signed-off-by: Michael Ehab <[email protected]> * style: modified deps.py file to follow pep 8 Signed-off-by: Michael Ehab <[email protected]> * Fixed some typos Signed-off-by: Michael Ehab <[email protected]> * Format code with Black and isort To ensure consistent code formatting, I used Black and isort to format the changed files. Signed-off-by: Michael Ehab <[email protected]> * Fix more typos in vulntotal tool Fixed more typos and formated the files Signed-off-by: Michael Ehab <[email protected]> * Use a consistent format for the docstring and maintain an imperative tone Changed the doctrings to have a consistent format and used Black and isort to format the changed files. Signed-off-by: Michael Ehab <[email protected]> * Handle TypeError and IndexError raised by get_item Signed-off-by: Keshav Priyadarshi <[email protected]> * Revert incorrect refactoring Signed-off-by: Keshav Priyadarshi <[email protected]> --------- Signed-off-by: Michael Ehab <[email protected]> Signed-off-by: Keshav Priyadarshi <[email protected]> Co-authored-by: Keshav Priyadarshi <[email protected]>
What
I modified the datasources files to follow PEP 8 more closely. They were already following it but they missed some small details like the docstrings. I also fixed some typos found in the vulntotal_utils.py file and other files.
Why
I made these changes to improve the readability and consistency of the code. Following PEP 8 helps to maintain a high standard of code quality and style. Fixing typos helps to avoid confusion and errors.
Anything else
Please let me know if you have any questions or feedback. Thank you for reviewing my PR!