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
feat(discoverability): add image cursor experience #1270
feat(discoverability): add image cursor experience #1270
Changes from all commits
199fcaf
f06b6d6
5ec96b6
e0f63c8
fcfd323
f4a20e1
4fa7784
7d4871b
5c353c0
d4d0080
c6a7647
275f74e
f0733f6
dd20098
7f48fcb
2e886d3
98a7b56
1784cb5
1f19789
a9a9ff7
5e069e0
ba28277
4d98138
20e15ec
be491b2
3353da4
cfab871
0b68ad0
b29629c
7fa2915
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.
AnnotationControlsFSM
has already been created inBaseViewer
constructor, right? Should we move the logic toBaseViewer
? Or call something likethis.annotationControlsFSM.setState
here?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 @ConradJChan and I discussed that we wanted ImageViewer to instantiate its own instance of AnnotationControlsFSM.
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.
Does it need to re-instantiate when
enableAnnotationsImageDiscoverability === false
? How about: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.
Let's also make sure that if
enableAnnotationsImageDiscoverability === false
, that we get the oldImageViewer
experience, i.e. not theenableAnnotationsDiscoverability
experienceThere 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.
Could you elaborate a little on this? Do you mean that we should have a check like this:
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.
Seems like this test may be combining too many things. Maybe split it out to a test based on
type
to make sure it doesn't get processed and the another test for the combinations ofcurrentState
and whether the image overflowsThere 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.
The
should
param is probably unnecessary. Maybe just update the test description to include theheight
andwidth
, otherwise consider breaking out a separate test to test thecurrentState
vsoverflow
conditions