Fixes #39246 - Add sorting and searching to the new Leapp preupgrade report#171
Conversation
7f9dd42 to
839459c
Compare
839459c to
9c13592
Compare
cf0a4d1 to
05b5b8a
Compare
|
@Lukshio do you mean searching? In my opinion, the new version is more consistent with the rest of the tables. |
05b5b8a to
9c4945f
Compare
@kmalyjur Yes, I meant search, anyway I didn't find way how to search for "Fix type" |
f93e38d to
d5da017
Compare
|
@Lukshio @adamruzicka it's ready for a re-review now. (sorry for all the pushes, I had broken rubycop) |
d5da017 to
c22140f
Compare
c22140f to
4ce7bf4
Compare
|
I fixed all the issues except for this one:
@Lukshio I didn't see it before, is it okay now? |
|
Added a custom layout for the preupgrade entries index endpoint to include |
e45ccd2 to
4c7cf07
Compare
I replaced this one test, however, I don't think it's necessary to replace the rest (13) of them, because they are going to be deleted when deleting the legacy leapp table. @Lukshio what do you think? Rebased. |
Sure, leave it as it is. |
adamruzicka
left a comment
There was a problem hiding this comment.
I'm not a huge fan of the custom layout. Normally I'd argue that those things will eventually deviate from the original they're supposed to be extending, but this one already does. Additionally I'd be worried that if the original changes, noone will remember to update this.
If this is strictly about showing the count when you select all, could that count be retrieved on demand? Once the user clicks that checkbox, it would make a call to the index endpoint and explicitly ask for fixable issues (maybe with per_page=0 since we just need the count)?
| protected | ||
|
|
||
| def model_of_controller | ||
| resource_scope |
There was a problem hiding this comment.
Judging by the method name, shouldn't this be "just" PreupgradeReportEntry?
…able_count" This reverts commit 71e7469.
|
It is now fetching the accurate count of fixable entries only when the user clicks "Select All". The commit 71e7469 using a custom layout was reverted. |
|
@kmalyjur Can you please provide screenshots/video of the issue with 0 select? I am probably not seeing/understanding the issue correctly |
|
@Lukshio Without the foreman core commit, the fixableCount is initially Screen.Recording.2026-07-01.at.15.22.40.mov |
| () => rawSelectedIds.filter(id => validFixableIds.includes(id)), | ||
| // eslint-disable-next-line react-hooks/exhaustive-deps | ||
| [rawSelectedIds.join(','), validFixableIds] | ||
| const selectAll = useCallback( |
There was a problem hiding this comment.
its causing number glitching between total and subtotal.
Screencast_20260701_190714.mp4
Lukshio
left a comment
There was a problem hiding this comment.
Core PR merged, changes looks good, packit tested
|
Thanks @kmalyjur @adamruzicka |





I’d appreciate an extra pair of eyes on the backend to confirm it's good, because I'm not sure about some parts.
EDIT: Dependent on theforeman/foreman#11060
Before:

After:
