-
Notifications
You must be signed in to change notification settings - Fork 1.5k
STY: Move _xobj_to_image to _xobj_image_helpers.py #3434
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
base: main
Are you sure you want to change the base?
Conversation
@stefan6419846 the changes in this PR caused an error with pillow import. Is an obvious fix? |
Do not import from |
Sorry still do not understand; which function(s) need the local imports? Is the reason for importing locally so |
An installation without Pillow should work until the user actually tries to export images using |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3434 +/- ##
=======================================
Coverage 97.07% 97.07%
=======================================
Files 56 56
Lines 9614 9614
Branches 1742 1741 -1
=======================================
Hits 9333 9333
Misses 168 168
Partials 113 113 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
@stefan6419846 please could you provide guidance for the coverage? |
|
Unsure how to do those tests. I would like to simplify the code in _xobj_image_helpers.py in a new PR, and then adding the tests may be easier. Do that in parallel? |
Analyze the code execution flow and set up the artificial data accordingly. There wouldn't be much of a difference when I would do this compared to you, except that you are already familiar with the specific code.
How do you imagine this? We would still have to merge on PR first. What are your refactoring plans? In general (as we already discussed for the page-specific JavaScript actions), please always outline such (non-trivial) changes beforehand to discuss them before attempting to do this, ideally in a proper issue, filling the provided issue template. (In theory, even this PR should have a corresponding issue for clarification first.) |
The refactoring is likely small, to make it more readable. Refactoring may be too strong a word here. And yes, may not help with the tests. |
No description provided.