alokai-cli core module #7099
alokai-cli core module #7099
Conversation
|
There was a problem hiding this comment.
Are there going to be tests? If not, please remove this file
There was a problem hiding this comment.
not in the core probably, removing
| .name("alokai") | ||
| .description("Alokai CLI is a tool to help you manage your Alokai projects") | ||
| .usage("[command] [options]") | ||
| .version("0.0.1", "-v, --version", "display the version number") | ||
| .action(() => { | ||
| program.help(); | ||
| }); |
There was a problem hiding this comment.
Isn't the exact same snippet in src/index.ts? Shouldn't the duplication be removed, as it looks like prebuild.js ins the main file?
There was a problem hiding this comment.
prebuild.js is used to generate src/index.ts dynamically based on alokai-* packages from node modules
|
Please also add changeset ( |
| ```typescript | ||
| import alokaiCli[YourPackageName] from 'alokai-[your-package-name]'; | ||
| ``` | ||
|
|
||
| Then, you can use the package in the `index.ts` file: | ||
|
|
||
| ```typescript | ||
| alokaiCli[YourPackageName].forEach((command) => { | ||
| program.addCommand(command); | ||
| }); | ||
| ``` | ||
|
|
||
| This will add the command to the core CLI application and will be available to use once the project is published. |
There was a problem hiding this comment.
Imo it's better to create an abstraction over the commands' registration. We could have a following API
import integrationCommands from "alokai-integrations";
const program = createAlokaiCli({
plugins: [
{ name: "integrations", commands: integrationCommands },
{ name: "modules", commands: modulesCommands },
//...
]
});or
import integrationCommands from "alokai-integrations";
const program = createAlokaiCli({
plugins: {
integrations: integrationsCommands,
modules: modulesCommands,
//...
}
});
🔗 Linked issue
❓ Type of change
📚 Description
📝 Checklist