-
-
Notifications
You must be signed in to change notification settings - Fork 23
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.
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
Add a registry for CLI Plugins #2
Comments
Hmm not sure if my comment here #1 might fits in better in this issue. Could you elaborate on the |
My first thought was how do we tell the cli what should be made available namespaced under this plugin. As an example for i18next we may want some |
Alright for now I am going to use this method until I hear otherwise :) |
Copying over @zewa666 's comment from the other issue - Great, installing through JSPM would also be a better alternative to the current Github download approach. With regards to cli what would you say if we expand that to an object which might contain the commands? Like:
EDIT: |
@zewa666 @ahmedshuhel @EisenbergEffect What do you guys think about including the cli plugins directly in the plugin registry instead of in a separate registry |
@PWKad I think it's an excellent idea under the circumstances. All the plugins are the part of larger Aurelia ecosystem. So having a common registry totally make sense. |
This issue is closed and we will incorporate the plugins into the main registry |
The registry should contain basic information about each plugin that is available for the CLI. To allow the registry to expand with additional properties, I propose we use an array of objects instead of a simple key:value pair. Example -
The text was updated successfully, but these errors were encountered: