[2.0] Ignite New

[GantMan]

ignite new should be started.

Take these examples as functional minimums. The actual experience can have spinners/friendly graphics etc.

version 1: Answers "no" to everything. Perfect for regen playground. Simply uses #568

ignite new SomeProject --min
Congrats! SomeProject has been generated

version 2: Answers "yes" to everything. Great for testing.

ignite new SomeProject --max
Congrats! SomeProject has been generated

version 3: Composer experience

ignite new SomeProject
Welcome to Ignite - The Unfair Headstart Generator

The following questions will help us choose your additional goodies.

Would you like the Ignite Development Screens? (y/n)
y
...
...
Congrats! SomeProject has been generated

[ericvera]

I've been playing with the v2 for the last couple of hours and have a v0.1 of the new command. It still needs some work, but thought I'd share it before investing too much on it. If this works let me know and I can create a pull request once I add a bit more validation. Otherwise let me know of any suggestions on a better approach.

Approach new.js:

1. Create a new directory (<new app name>) under the current working directory
2. Call ignite add ignite-basic-structure <new app name> using the new directory as the cwd

Considered Approach:

• Call cli.js directly and require the ignite-basic-structure generator directly. Since each of those deal directly with the parameters passed to the command line, that would require refactoring the code to be able to pass the valued from the new command.

[kevinvangelder]

@ericvera Looks like a great start to me, but @GantMan and @skellock are the real masterminds, so I'd look for their feedback before continuing. This already covers most of the functionality of the proposed --min option.

[ericvera]

There are a few things that I am still not sure what your intended design is. Did you intend to run react-native init <project name> (I have not added this yet) and then run the ignite-basic-structure generator?

[skellock]

Thanks for the input @ericvera. I'd like to see ignite-basic-structure rolled into ignite personally.

I think you'll see a lot of refinements next week though as the team is getting together in person.

And yes, our starting point is react-native init EricApp.

[skellock]

@ericvera I just re-read your comment. I didn't realize what you were saying is: you're building it.

@GantMan has built new and we're just tweaking it now. We're going in stages. We've got unholy (what we're calling ignite 1's kitchen sink approach) up & running now, and we're going to bust those into plugins next.

I appreciate the help though. Perhaps what we can do is start tagging a few tasks with Help Wanted on Ignite 2 going forward.

[GantMan]

awesome thoughts @ericvera - I think Ignite 2.0 in one week will look very different. Keep your ear to the ground here on github to see the transformation as we go through it 👍

[GantMan]

@skellock , should this have been closed?

[skellock]

I think so. ignite new has been built.

Feel free to open this up if you think i'm overlooking something.

[GantMan]

Just thinking the --min --max hasn't been put in yet. The original ticket had those.

[skellock]

Okie dokie.

[kevinvangelder]

@ericvera We made a lot of progress on 2.0 this week. Feel free to check out the latest code on next as well as the new issues we've filed to get an idea of where we could use help.

[skellock]

Done.