Closed alessandrofelder closed 10 months ago
Patch coverage: 100.00%
and project coverage change: +5.47%
:tada:
Comparison is base (
76733ed
) 91.85% compared to head (232371b
) 97.32%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
I am going to fix the slight decrease in coverage, but in the meantime it would be great if, @adamltyson, you could check that you agree that nothing is broken for the user by this PR (it's supposed to be a pure moving-stuff-around and communicate-via-qt-signals-instead PR) with no changes in functionality for the user?
Description
What is this PR
Why is this PR needed? The
atlas_viewer_widget.py
file was becoming unwieldy to add functionality to, and things that were napari-independent were tested in a napari context as a consequence of the previous architecture (which made the tests slow, as well as violating separation of concerns).What does this PR do?
This PR splits the classes more independent and have clearer responsibilities. Some things have been renamed for clarity too. The plugin should look and behave exactly the same as before (bar also fixing #66 ) a key advantage is better modularity
a downside is that there is an extra layer of abstraction in the code(but I think it's worth it!)
References
Closes #8 Closes #66
How has this PR been tested?
Tests have been refactored accordingly, and pass. Also extensive manual testing for any unintentional changes in behaviour.
Is this a breaking change?
Not for the user, big change in API which is good to be done early in the development process for this plugin
Does this PR require an update to the documentation?
Will be added as part of #52. Docstrings improved and added as needed by the refactoring.
Checklist: