-
Notifications
You must be signed in to change notification settings - Fork 44
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
🐛 Applications: bulk delete disabled when no selection #1149
Conversation
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #1149 +/- ##
=======================================
Coverage 44.08% 44.08%
=======================================
Files 177 177
Lines 4500 4500
Branches 1008 1008
=======================================
Hits 1984 1984
Misses 2505 2505
Partials 11 11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Just a minor nitpick
@@ -419,6 +419,9 @@ export const ApplicationsTableAnalyze: React.FC = () => { | |||
importWriteAccess = checkAccess(userScopes, importsWriteScopes), | |||
applicationWriteAccess = checkAccess(userScopes, applicationsWriteScopes); | |||
|
|||
const areAppsInWaves = () => |
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.
This doesn't need to be a function, it can just be a boolean variable. It is immediately called twice in the same render when it only needs to run the some
loop once
@@ -608,6 +608,9 @@ export const ApplicationsTable: React.FC = () => { | |||
importWriteAccess = checkAccess(userScopes, importsWriteScopes), | |||
applicationWriteAccess = checkAccess(userScopes, applicationsWriteScopes); | |||
|
|||
const areAppsInWaves = () => |
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.
Same here
…ecated `DropdownItems`, use `isAriaDisabled` prop for items with tooltips (#1150) Fixes a regression caused by #1126 where dropdown items that are disabled with tooltips could not trigger the tooltips. Discovered by @gildub when working on #1149. It appears the `isAriaDisabled` prop which we need for retaining the mouse hover event on a disabled DropdownItem is not present in the new PF5 DropdownItem. This is due to missing styles in PF core that are still being addressed (see patternfly/patternfly#5528, patternfly/patternfly#5692, and related comment here: patternfly/patternfly-react#8992 (comment)) Until `isAriaDisabled` is supported in the new PF5 DropdownItem we must restore the usage of the deprecated component for these tooltips to work.
Signed-off-by: Gilles Dubreuil <[email protected]>
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 👍
…election (#1149) (#1153) Resolves https://issues.redhat.com/browse/MTA-898 (cherry picked from commit 807e094)
Resolves https://issues.redhat.com/browse/MTA-898