-
Notifications
You must be signed in to change notification settings - Fork 6.7k
feat: Zoom in and out on resource view (#7183) #8290
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
Conversation
06dfdb6 to
1e37969
Compare
Codecov Report
@@ Coverage Diff @@
## master #8290 +/- ##
==========================================
+ Coverage 41.63% 41.93% +0.29%
==========================================
Files 174 176 +2
Lines 22881 22992 +111
==========================================
+ Hits 9527 9641 +114
+ Misses 11990 11966 -24
- Partials 1364 1385 +21
Continue to review full report at Codecov.
|
1e37969 to
ddac8f4
Compare
Signed-off-by: Keith Chong <[email protected]>
ddac8f4 to
e35bfdf
Compare
rbreeze
left a comment
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! I'd like @alexmt to confirm before merging if he has time
alexmt
left a comment
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.
That is just awesome!
Can we persist zoom settings in user preferences for consistency? This definitely can be done later.
LGTM
|
This is such a cool feature! |
Signed-off-by: Keith Chong <[email protected]> Signed-off-by: pashavictorovich <[email protected]>



Signed-off-by: Keith Chong [email protected]
About this PR:
Addresses #7183
This zoom implementation is strictly transformation, which is option/solution A. Panning is limited to scrolling of the enlarged rectangular area, and isn't truly panning of a view-box typical of SVG graphics. For option B, we could convert to all SVG but its performance degrades for many rendered objects. I've investigated this more and there is a bit of work involved.
Zoom level is not made a view preference on the details page so that the UI in multiple browser tabs can have different zoom values. Drawback is that the zoom level will reset each time you exit and enter the details page, and it's different behavior than the grouped-node button. However, zoom level is maintained when switching from tree view to network view and vice versa.
Grouped-node button moved to floating graph toolbar. Zoom buttons similar to the ones seen in the Argo Workflows UI.
CSS and tool bar can be moved to argo-ui, but is not part of this PR
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist: