Closed danepowell closed 5 years ago
Great idea. It'd also be good to remove the dependency on Lightning Dev. +1 from me either way. We could do the lightning_dev dependency in a follow up.
I added a step to remove lightning_dev. It's maybe not ideal, since you have to wait for composer to install it and then remove it--it would be nice if it never existed it the first place.
I'm actually not sure why lightning_dev exists in the first place if we're just going to remove it, is it for automated tests or something?
I'm also not sure why tests are failing, the failures seem unrelated.
I'm also not sure why tests are failing, the failures seem unrelated.
Indeed. We need to get those fixed. Will prioritize today.
After chatting with @phenaproxima, we decided to try a slightly different tack. Instead of distributing lightning_dev and forcing everyone to remove it after project creation, let's get it out of composer.json and just have the automated tests require it when necessary.
I'm in favor of merging this when it's green on Travis.
Opened #92 to broaden the scope a bit.
Fixed by #93.
Currently when you create a new project, you get a copy of lightning-project's .travis.yml. That seems like unneeded cruft for downstream projects. This removes .travis.yml after a project is initially created.