Skip to content

Conversation

@taooceros
Copy link
Member

@taooceros taooceros commented Feb 12, 2021

fix #265

TODO:
create an interface for cleaning up plugin information if they store setting or some data.



Core.Plugin.PluginManager.Settings.Plugins.Remove(plugin.ID);
Core.Plugin.PluginManager.AllPlugins.RemoveAll(p => p.Metadata.ID == plugin.ID);
Copy link
Member

Choose a reason for hiding this comment

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

if we can do this, does this mean no restart is required?

Copy link
Member Author

Choose a reason for hiding this comment

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

Well, we still cannot unload assembly unless we use the library @JohnTheGr8 has mentioned, but we can load assembly dynamically, which means that installation may not require restart.

@jjw24
Copy link
Member

jjw24 commented Feb 13, 2021

This is ready for review?

@taooceros
Copy link
Member Author

This is ready for review?

yes, it is a simple change and it works

@jjw24 jjw24 added this to the 1.7.1 milestone Feb 13, 2021
@jjw24 jjw24 added the bug Something isn't working label Feb 13, 2021
@jjw24 jjw24 enabled auto-merge February 13, 2021 10:44
@jjw24 jjw24 merged commit f2b7367 into Flow-Launcher:dev Feb 13, 2021
@jjw24 jjw24 mentioned this pull request Feb 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PluginsManager does not clean up user settings after plugin removal

2 participants