-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Create sub package as a plugin #147
Comments
I don't think a default folder where a plugin has access to write stuff will work. Project structures are too different and I don't want sidekick to force one. But, there are two things sidekick could help you with:
But, Plugin Settings, might be unnecessary. Checkout the current implementation of |
It would be nice if we could just move the method from the |
Which code do you mean? All you need is a relative path from a fixed location. Sidekick already provides: Repo root// in install.dart
final serverDir = findRepository().root.directory('server'); // in sidekick cli
final serverDir = repository.root.directory('server'); Both point to the same location sidekick cli package location// in install.dart
final serverDir = PluginContext.sidekickPackage.root.directory('server'); // in sidekick cli
final serverDir = Repository.cliPackageDir.root.directory('server'); Both point to the same location |
@passsy I think we can close this |
As a plugin we create a new folder for the
dockerize
command calledserver
.We create it by hand and later when we need to reference it we need to find it ourselves.
Would it be wanted and feasible to have a
addPackage
function in theplugin_installer
?It would be cool to have the project's structure abstracted away for plugins.
I imagine this creates a folder in the right place. Be it the
packages
folder or top level if nopackages
folder is present.Then introduces this folder in the
<cli>_project.dart
.The text was updated successfully, but these errors were encountered: