-
Notifications
You must be signed in to change notification settings - Fork 59
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
fix: prevents collapsing of execution errors when scrolled out of view #80
Conversation
Codecov Report
@@ Coverage Diff @@
## master #80 +/- ##
==========================================
+ Coverage 63.06% 63.16% +0.10%
==========================================
Files 363 363
Lines 5686 5699 +13
Branches 842 845 +3
==========================================
+ Hits 3586 3600 +14
+ Misses 2100 2099 -1
Continue to review full report at Codecov.
|
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.
1 suggestion inline 👍
Co-authored-by: Bob Nisco <[email protected]>
## [0.7.3](http://github.com/lyft/flyteconsole/compare/v0.7.2...v0.7.3) (2020-07-06) ### Bug Fixes * prevents collapsing of execution errors when scrolled out of view ([#80](http://github.com/lyft/flyteconsole/issues/80)) ([ba39c1c](http://github.com/lyft/flyteconsole/commit/ba39c1c9c0783d69aee48de2f1b666879472e6b8))
🎉 This PR is included in version 0.7.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
flyteorg/flyte#64
Since we use virtualization, the components used to render the rows in this table are unmounted every time they leave the viewport. This is great for performance, but it resets state when the component comes back into view. To account for this, we're now storing the expansion state for errors at the table level, and piping them through as an initial state when mounting the components. This will maintain the expansion state when the component leaves and reenters the viewport.
Note: This change should have a corresponding unit test. However, since jsdom does not support layout, we can't test scrolling the component out of the viewport and back in. So it's not possible at the moment to write a unit test for it :-(
Before:
After: