You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Download the plugin at the specified version (or latest if none was given)
Run <plugin>/tool/update.dart and pass it the name of the cli, the currently installed plugin version, as well as the target version
The update.dartscript must be implemented by the plugin author. If possible, he can implement automatic migrations. If there are breaking changes without automatic fixes, information messages can be printed or thrown here.
Update the minimum constraint of the plugin dependency in the cli
Update check
How do we let the user know that an update for one of his plugins is available?
It would be nice to do an update check for a specific plugin only when a command of that plugin is run. However, I don't know how we can map the plugin which is currently being run to the plugin it comes from.
An easier way would be to do an update check for every installed plugin when running any command except the PluginsUpdateCommand.
But how do we know which plugins have been installed to the cli?
We could save the information in the sidekick section of pubspec.yaml. A list of all plugins which have been installed under sidekick: plugins: [...]. When installing a plugin, we add its entry to that list.
Read all direct dependencies from the cli's pubspec.yaml. Filter dependencies which themselves have a direct dependency on sidekick_plugin_installer - those are sidekick plugins.
The text was updated successfully, but these errors were encountered:
Maybe a short addition it would be great to see which plugins are installed from the CLI
cm plugins list
You have following plugins installed
> plugin_one
> plugin_two
Another idea is like a favorite plugins that will be visible. Something like:
cm plugins remote list
- [x] sidekick_vault - A short descritption
- [ ] dockerize_sidekick_plugin - A short description
You can find more relevant plugins here: https://pub.dev/packages?q=topic%3A+sidekick-plugin
We should add a command for updating plugins which have been installed to a sidekick cli.
PluginsUpdateCommand
The usage could look like this:
<my_cli> sidekick plugins update <plugin> [version]
The implementation can be similar to
UpdateCommand
<plugin>/tool/update.dart
and pass it the name of the cli, the currently installed plugin version, as well as the target versionupdate.dart
script must be implemented by the plugin author. If possible, he can implement automatic migrations. If there are breaking changes without automatic fixes, information messages can be printed or thrown here.Update check
How do we let the user know that an update for one of his plugins is available?
It would be nice to do an update check for a specific plugin only when a command of that plugin is run. However, I don't know how we can map the plugin which is currently being run to the plugin it comes from.
An easier way would be to do an update check for every installed plugin when running any command except the
PluginsUpdateCommand
.But how do we know which plugins have been installed to the cli?
sidekick
section ofpubspec.yaml
. A list of all plugins which have been installed undersidekick: plugins: [...]
. When installing a plugin, we add its entry to that list.pubspec.yaml
. Filter dependencies which themselves have a direct dependency onsidekick_plugin_installer
- those are sidekick plugins.The text was updated successfully, but these errors were encountered: