-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Show the warning message in the case with deprecated plugins #14707
Conversation
@slemeur WDYT? |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
ci-test |
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Is it migrating or upgrading ? |
I think it could be an upgrading in the case when we just upgrade the version of the same plugin. But it can be a migration too. |
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 to double-check, does the warning only appear on the Plugins tab, or whenever workspace details are opened?
@amisevsk The warning only appears on the Plugins tab. |
I think I understand why that is the case, but also worry that a user might never see it (I don't know how often a user would visit the plugins/editors tab for an already set up workspace). +1 on the changes, regardless. |
Based on the video shared here: https://www.youtube.com/watch?v=qkjxKXLGZ70&feature=youtu.be
The workspace uses deprecated plugins. Upgrade the plugins to their latest version by pressing the button Upgrade plugins.
This is unclear. Which icon user has to press? It's a warning icon, a user will not expect to be able to click on it to fix the problem. I would remove the action from the button, and just explain what to do. For editors
The workspace uses deprecated plugins and editor. Upgrade to the latest versions available by pressing the button Upgrade plugins.
I find the experience a bit challenging and confusing for a end-user. Should the action be closer to the error message? Could you have "Click Here to upgrade all deprecated components" at the end of the error message, which will trigger the action ? cc @evidolob . |
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
@slemeur Is it ok for you? |
E2E tests of Eclipse Che Multiuser on OCP has been successful:
|
dashboard/src/app/workspaces/workspace-details/workspace-details.service.spec.ts
Outdated
Show resolved
Hide resolved
dashboard/src/app/workspaces/workspace-details/workspace-details.service.spec.ts
Outdated
Show resolved
Hide resolved
dashboard/src/app/workspaces/workspace-details/workspace-details.service.spec.ts
Outdated
Show resolved
Hide resolved
...board/src/app/workspaces/workspace-details/workspace-plugins/workspace-plugins.controller.ts
Outdated
Show resolved
Hide resolved
...board/src/app/workspaces/workspace-details/workspace-plugins/workspace-plugins.controller.ts
Outdated
Show resolved
Hide resolved
dashboard/src/components/api/workspace/che-workspace.factory.ts
Outdated
Show resolved
Hide resolved
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
Signed-off-by: Oleksii Orel <oorel@redhat.com>
E2E Happy path tests of Eclipse Che Single User on K8S (minikube v1.1.1) has been successful:
|
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.
Thanks! Nice work, Oleksii!
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
Signed-off-by: Oleksii Orel oorel@redhat.com
What does this PR do?
Add implementation of the warning message in the case with deprecated plugins and the possibility to auto-migrate plugins by pressing the button.
What issues does this PR fix or reference?
Needed for #13021
Release Notes
Docs PR
https://youtu.be/7U00YxALrFE