Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Me and Luke are working on a little refactor of how the UpdateManager works...
It also includes some components from my old composer PR found here: #967
The core idea of this is that there should be consistent interfaces to interact with different things built on top of Winter (i.e.
modules
,plugins
&themes
). Each of these elements will now have their class (i.e.Theme
,PluginBase
,ModuleServiceProvider
) will now extendWinterExtension
which will allow them to all interact with the update manager and other system functions directly.In addition
PluginManager
,ThemeManager
&ModuleManager
(new) will all implement theExtensionManager
interface, which will allow for a consistant way to interact with all Winter extensions.I.e. You will be able to call
PluginManager::instance()->update($plugin)
orThemeManager::instance()->update($theme)
.This also allows us to do some cool stuff like (only support for plugin installing is currently functional)
By the end of the PR, the UpdateManager as is may no longer exist as is, instead each
ExtensionManager
will be responsible for it's existing functionality.