Open dinkopehar opened 2 years ago
Possible alternative/related:
Write all available options into the generated shard.yml
(atm at least crystal: <version>
is missing, possibly others)
Unify shards init
and crystal init
?
Might be just me but I often type the former by accident when I actually meant the latter.
Personally I don't see a need for interactive prompting since shard.yml
is so easy to write (unlike e.g. package.json
in npm).
@m-o-e I agree it's a simple file to write (shard.yml
). Maybe in future, if this file contained more information (all package manager files at one point contain lot of info), it would be nice to have it created interactively. On the other hand, I see some of the described keywords in man shards
are missing on shard init
. This is not important feature at the moment.
NPM and some other package managers have the ability to generate their versions of
shard.yml
file based on user provided input. Similar to those package managers, when we executeshards init --interactive
, it should ask user for basic input, such as package name, author name etc. The fill in provided data into theshard.yml
Where
shard init
can generate basicshard.yml
file, maybe this option can ask for more details of everything that can go insideshard.yml
, such as target, homepage, repository etc