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.

Sign up for GitHub

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

Jump to bottom

Refresh frontend/backend plugin parts on plugin disabled state #9211

Closed
ashumilova opened this issue Mar 23, 2018 · 2 comments
Closed

Refresh frontend/backend plugin parts on plugin disabled state #9211

ashumilova opened this issue Mar 23, 2018 · 2 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@ashumilova
Copy link
Contributor

Provide a way to refresh the whole frontend/backend plugin parts if a plugin is disabled and user want to be sure it’s cleanly removed.
@ashumilova ashumilova added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/ide2 kind/enhancement A feature request - must adhere to the feature request template. labels Mar 23, 2018
This was referenced Mar 23, 2018
Closed
Closed
@slemeur
Copy link
Contributor

slemeur commented Mar 26, 2018

What options are you considering?

What is the purpose, for the end user to ensure that it has been cleanly removed?
When the user is disabling a plugin, he is naturally expecting that the plugin will be removed cleanly. We should consider displaying a status of the plugin and when it is disabled, display an update to the user via a notification.

@ashumilova ashumilova added severity/P2 Has a minor but important impact to the usage or development of the system. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Apr 12, 2018
@che-bot
Copy link
Contributor

che-bot commented Sep 7, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2019
@che-bot che-bot closed this as completed Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ashumilova @slemeur @che-bot