-
Notifications
You must be signed in to change notification settings - Fork 7
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
Refactoring #46
Refactoring #46
Conversation
Codecov Report
@@ Coverage Diff @@
## master #46 +/- ##
==========================================
- Coverage 95.32% 93.83% -1.49%
==========================================
Files 7 6 -1
Lines 363 259 -104
==========================================
- Hits 346 243 -103
+ Misses 17 16 -1
Continue to review full report at Codecov.
|
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.
First comment, will finish the review later :) thanks!
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.
overall looks good. files and functions more specific and informative.
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.
resolve that linting error. I'm fine merging when Nina is.
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.
Very nice, thank you!
BTW: are you using pycharm or vscode with the functionality that allows refactoring quickly? E.g. vscode has an option "change all occurences", which is convention for this (see screenshot).
It is looking much better, thank you very much for your patience in this!
I have made some comments on the conventions regarding the names of the input parameters in the functions now (which is in the same spirit of my previous remarks on the file names and function names, now we're looking more granularly at the parameters' names).
The parameter names should also follow a consistent convention (otherwise the user gets crazy because they needs to remember that write_atomic_model_*
takes output_path
as first parameter, but write_micrograph_*
takes path
as first parameter and write_metadata_*
takes path
as second parameter : not a great experience.
I have made comments along these lines, but I'll let you go through the files to see if, in this spirit, everything can be made rigorously consistent.
Thanks!
And yes, please fix the linting error. It might be coming from an update in black, it has been popping up on other projects that I manage. It could be fixed by running |
@ninamiolane Changes implemented, please let me know if there's anything else that can be better represented! |
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.
LGTM! Thank you for the changes.
Refactored according to Nina's requests - reorganized file structure and renamed many functions accordingly.