Scaffolding should have it own command. Something like hal component scaffold would be the most descriptive. The command could work interactively or using arguments and allow us to scaffold projects like we do now.
Then hal component create would have a narrower scope and it would be easier to explain what it does.
Some technical concerns around this suggestion, is that we will have to ask the user twice about the runtime, which is bad ux.
To overcome this issue, we could save information like the runtime, the version etc in a .hal file, that will be created when we scaffold.
An alternative would be to implement a mechanism to detect the target runtime, using parsing of known project models (maven, gradle, npm).
Per @iocanel:
Scaffolding should have it own command. Something like
hal component scaffold
would be the most descriptive. The command could work interactively or using arguments and allow us to scaffold projects like we do now.Then
hal component create
would have a narrower scope and it would be easier to explain what it does.Some technical concerns around this suggestion, is that we will have to ask the user twice about the runtime, which is bad ux.
To overcome this issue, we could save information like the runtime, the version etc in a .hal file, that will be created when we scaffold.
An alternative would be to implement a mechanism to detect the target runtime, using parsing of known project models (maven, gradle, npm).