would be handy, just to create the default example project with no prompts. But I think the shortcut specifying the project name would be a good option, and if it was handy enough maybe something like
sushi init -name MyIG -version 0.10
which sort of leads on to maybe exposing more of the config options such as canonical, fhirVersion etc.
I think being able to set a version could be possibly be useful for CI, as well as minimising required changes in config for the project after creation.
The original reason I was looking at this was to create a package using the standard tooling for test automation, so being able to version and name the project so it ended up in the package json would be very useful in that context. Although a little convoluted just to create a package, but I couldn't see more minimal approach that used the standard tool chain
@cmoesel
I was initially thinking something like
sushi init -ywould be handy, just to create the default example project with no prompts. But I think the shortcut specifying the project name would be a good option, and if it was handy enough maybe something like
sushi init -name MyIG -version 0.10which sort of leads on to maybe exposing more of the config options such as canonical, fhirVersion etc.
I think being able to set a version could be possibly be useful for CI, as well as minimising required changes in config for the project after creation.
The original reason I was looking at this was to create a package using the standard tooling for test automation, so being able to version and name the project so it ended up in the package json would be very useful in that context. Although a little convoluted just to create a package, but I couldn't see more minimal approach that used the standard tool chain