-
Notifications
You must be signed in to change notification settings - Fork 158
WIP: Extend column mgmt for general conditional columns #16356
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: dv/ROX-30477-replace-redux-for-metadata
Are you sure you want to change the base?
WIP: Extend column mgmt for general conditional columns #16356
Conversation
This change is part of the following stack: Change managed by git-spice. |
Skipping CI for Draft Pull Request. |
a1cccef
to
9b91975
Compare
12024f5
to
9343f39
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## dv/ROX-30477-replace-redux-for-metadata #16356 +/- ##
========================================================================
Coverage 49.12% 49.12%
========================================================================
Files 2632 2632
Lines 195130 195130
========================================================================
Hits 95862 95862
Misses 91770 91770
Partials 7498 7498
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
9343f39
to
302a952
Compare
/test gke-ui-e2e-tests |
@dvail: No presubmit jobs available for stackrox/stackrox@dv/ROX-30477-replace-redux-for-metadata In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Description
Expands the usage of column management to allow cleaner conditional rendering of table columns in Vuln Management.
This will help us to use these tables in the OCP dynamic plugin, which has different column requirements, without requiring us to do any of the following:
In addition to avoiding the previous items there are a couple of side benefits to this approach:
colSpan
getVisibilityClass
helper, which is already in use and consolidates the multiple render patternsFollow ups
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Existing thorough tests at the unit and e2e level regarding column management in VM 🙏
Manual testing with feature flags, etc. (screenshots TBD)