Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Bugfix] For
layer_attributes
that are dict (likecolor
) do key/value comparisons #181[Bugfix] For
layer_attributes
that are dict (likecolor
) do key/value comparisons #181Changes from 20 commits
05122db
66ef255
d273e69
6f812d6
c295663
ff2db17
46adce5
96299e8
58b1dba
2411da0
01761f8
470c685
24b54a8
ff31cf6
c21c760
384e2a3
a183ce8
4df23b5
e891efe
86acb74
3e3da4f
106365b
f5130d8
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Can we drop these lines now, for the same reason as the surface hack? Or maybe do something like:
or something like this? I don't like that this stuff is "hardcoded" in the test...
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.
(also,
arn't
is a typo. 😜)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.
Metadata isn't captured
napari-animation/napari_animation/viewer_state.py
Lines 17 to 19 in 35e5acc
and it's popped in viewer_state
napari-animation/napari_animation/viewer_state.py
Line 34 in 35e5acc
So I think that one has to be popped.
data
doesn't get captured either:https://github.com/napari/napari-animation/blob/35e5accac9c6994b9735bc7ecb1d679e2b70bdc5/napari_animation/viewer_state.py#L30C43-L31
Only the 2 element of the tuple is used.
While it could be cool if it worked, I'm not sure how keyframes and interpolation would work with data.
So the idea in the test would be to make a NEVER_CAPTURED_ATTR variable at the top of the file and put those there?
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.
I a user wants to use napari-animation to change smoothly change the contents of
data
through out, there's a very good chance they actually need to add a dimension toDims
and use that instead :PThere 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.
Should this test assert something? like that an exception is not thrown? I mean if there is an exception then it's a fail--like on main with this test--so maybe this is fine?
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.
I think it's just checking that there's no exception, yes. You could add an assert later that the viewer did indeed change, but maybe that's tested elsewhere?