Skip to content
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 #21641 - Drop jquery-ui spinners in favor of React implementation #8538

Merged
merged 1 commit into from
Jun 14, 2021

Conversation

yifatmakias
Copy link
Contributor

No description provided.

@theforeman-bot
Copy link
Member

Issues: #21641

@ezr-ondrej
Copy link
Member

The failures are definitelly not relevant, probably some npm package update?
I'll investigate next week if noone would get to it sooner.

@MariaAga MariaAga self-assigned this May 26, 2021
@MariaAga
Copy link
Member

MariaAga commented May 26, 2021

This shouldn't be merged before it's usage is removed in plugins:
https://github.com/search?q=org%3Atheforeman+numFields&type=code
Also the deprecation says that it will be only removed in foreman 3.0

@ezr-ondrej
Copy link
Member

ezr-ondrej commented May 26, 2021

This shouldn'd be merged before it's usage is removed in plugins:
https://github.com/search?q=org%3Atheforeman+numFields&type=code
Also the deprecation says that it will be only removed in foreman 3.0

there is multiple levels to answer this.

  1. 2.6 = 3.0 I'm just working on writup for it
  2. plugins had time to do that, we should not be as concerned with plugins using some deprecated stuff
  3. to ease the point 2, because we gave just one version to plugins to deal with this, the function calls can probably be just removed, as we have changed the helpers implementation to react implementation, so the initializers in the plugin just dosn't do anything

This being sad, we could leave blank function with the deprecation warning only for one more version, so the plugins don't get js errors just by calling useless function.
EDIT: Though I would just prefer plugin maintainers to remove the calls and also by that verify the new implementation is working for them. It is simple removal and simple test, that IMHO is not too much to ask from plugin maintainers if they wish to keep the plugins alive.

@ekohl
Copy link
Member

ekohl commented May 26, 2021

If it's a simple migration, it can be beneficial (and faster) to submit a PR yourself.

@@ -46,7 +45,6 @@ window.tfm = Object.assign(window.tfm || {}, {
hosts,
httpProxies,
toastNotifications,
numFields,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can imagine having in this file

const numFieldsDeprecationOnly = {
  initAll: () => { window.tfm.tools.deprecate('initAll()', 'does nothing as of now, please stop calling it',    '3.2') };
};

And then here: numFields: numFieldsDeprecationOnly, Which would prevent plugins from failing hard on the function missing for two more version.

Copy link
Member

@ezr-ondrej ezr-ondrej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work!
Just noticed we are leaving some bits behind, can we drop these requires? :)

@theforeman-bot theforeman-bot added Waiting on contributor Legacy JS PRs making changes in the legacy Javascript stack and removed Waiting on contributor labels Jun 14, 2021
Copy link
Member

@ezr-ondrej ezr-ondrej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @yifatmakias ! Great drop 👍

@ezr-ondrej ezr-ondrej merged commit b55d3ed into theforeman:develop Jun 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Legacy JS PRs making changes in the legacy Javascript stack Needs testing UI Waiting on contributor
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants