What should we call the CLI tool?

i like "spark"

it's kind of nostalgic,
if you know what I mean...

I really like this too. This will probably be our winner. I had thought about ignite as someone else mentioned but it didn't feel quite right. Spark, though, has the right implications and the nostalgia to boot.

+1 for the spark! I liked it back then!

@kilishan Is it possible to include your Vulcan CLI extension to the base CI4 project? A basic scaffolding tool would be nice, and if you include it then we have the name too!

When it was first discussed a couple of years, there was some pretty vocal opposition to the idea of code generators in the framework. I cheated a little with the Migrations generator because of all of the other migration tools that just really felt necessary, but don't imagine that it will make it into the framework itself. My hope is that it might get picked up as an official first-party library under the CI umbrella, but nothing about that has been discussed internally, other than some initial talks when this all got started about keeping that as a potentially separate tool, if it was created at all, similar to how Phalcon handled it.

Time will tell.

https://spark.apache.org/trademarks.html


@sv3tli0
common practice is to use spaces and not tabs, but ci use tabs.
I do not see any reason to remove the extension.