crystal build without spepecified program files

[tbrand]

Hi all,

Currently, crystal build is not working without specified program files but just shows the usage.
But given the fact that almost all projects are created by crystal init, I think crystal build should work in that case.
I added a feature to the crystal command that crystal build works in a root directory of the project created by crystal init.
When user doesn't run crystal build in a root directory of a crystal project, it works as the same as before.

Best

[ysbaddaden]

IMHO this is out of scope for crystal. Having a command work in one context (unrelated to the command) but not in another is confusing.

This would fit better into Shards. See crystal-lang/shards#110

[tbrand]

Hi ysbaddaden,

Thanks for your comment and suggestion!
Considering the both of features of crystal and shards command, the feature I added is much fit for crystal not shards
Because shards init doesn't construct whole project but only creates a shard.yml.
On the other hand, crystal init does it and ensures that project contains shard.yml.
So I think crystal build building a shards project by default is quite natural.
Any comments are welcome :)

Best

[bcardiff]

Some apps will be made up of many executables. So you will need to be explicit on those. Having this kind of default might hide the users how simple is to choose an entry point.

Also some tools need to know which is the entry point. If there is no introspection for this, the logic will end up duplicate.

I would feel more comfortable with a solution described in the shards issue linked before.

I like the default, but i would make it work due to default values in a shard.yml or some other build artifact rather than the code for the reasons i describe here.

[tbrand]

Hi bcardiff

Hmm, OK.
I will work on it with shards :)
Thanks for your comments!