-
Notifications
You must be signed in to change notification settings - Fork 994
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
Fixes #37390 - drop jquery-ui #10142
Conversation
I'll check if Katello uses jquery-ui or are those just leftovers |
If they still are, I wonder what else is silently relying on it. If other plugins don't then we could consider moving it to katello, until it's dropped there |
Added a PR to Katello Katello/katello#10982 |
In https://github.com/theforeman/actions?tab=readme-ov-file#foreman-plugin-ruby-tests I've added documentation on how to run CI for plugins against this PR. You'd use |
3cbb02e
to
ad8b703
Compare
Do we expect the checks here to turn green now that the katello pr was merged or is there anything else that needs to happen? |
ad8b703
to
76fa857
Compare
The test failures look unrelated, but I wonder how those ever passed. I don't think that code path was ever supposed to be valid because |
#10410 should fix that. Could you rebase? |
76fa857
to
dff34bc
Compare
The Katello error looks related:
When I check |
@ekohl What are |
Isn't that just regular scss? So https://sass-lang.com/documentation/at-rules/import/ |
@ekohl It seems that |
Looking at https://github.com/jquery-ui-rails/jquery-ui-rails/tree/master?tab=readme-ov-file#require-everything I get the impression this was never valid but somehow worked anyway. Now I look further, I see that this is probably the line that really triggers it: That looks correct if I look at https://github.com/jquery-ui-rails/jquery-ui-rails/tree/master?tab=readme-ov-file#widgets. Perhaps easiest to try to get it to work locally and then open a PR to Katello that adds the right requires and point it to this PR (https://github.com/theforeman/actions?tab=readme-ov-file#foreman-plugin-ruby-tests has a section on testing against a specific PR using I was digging a bit deeper and I see it's used in 1 place: Then the customAlert function is only called here: Do I read it right that it tries to replace Sadly, the progressbar is used on the sync management page. I know there's a planned effort to rewrite it, but perhaps @jeremylenz or @parthaa know more about that progress. |
There's currently no plan to rewrite Sync Status. (ERB is quite stable, as you know ;) But if you need to remove this I'm sure we can shove a React progress bar in there or figure something else out. |
Adding |
Oh yes, that must be it. I think with just Foreman it looks at the bundler config and relies on bundler to require it. For plugins that doesn't work and it needs to be explicit. That sounds like the correct fix to me.
It's more about getting rid dependencies and right now that page means we need to continue including jquery-ui. |
Thanks, added: Katello/katello#11274 |
Now that's merged I just kicked off the failed tests again. |
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.
Current Katello test failures look unrelated. @adamruzicka agreed we can merge this now?
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.
Aye, let's get this in
Thank you @MariaAga , @jeremylenz & @ekohl ! |
Last use was in b55d3ed
didnt find any other use for the jquery-ui js or css