What's strange, the generated tests do the same thing and don't generate errors.
But keep the
beforeEach call the way it is.
_userOptions_ is injected into the beforeEach and stored in the userOptions variable within the describe function. But then each of your tests has a userOptions parameter defined its arrow function. So your tests using the userOptions from the arrow function, not the one defined in the describe function.
Make sense?
ohh! never mind, I got the answer here: https://github.com/Swiip/generator-gulp-angular/blob/master/docs/how-it-works.md
(using a newer generator version)
Really it's the time tested answer of "It depends".
In my case I had been working on the project for about a month using Angular 1.3. Then Angular 1.4 came out and the generator got an update. So naturally, I wanted to update the generator as well as Angular (just updating Angular would have been far easier). This was about the time when the index module got broken into several files, which I was already trying to do myself. So I upgraded. It wasn't pretty. It was a pretty labor intensive process to move all the code around into the necessary places.
I think this is a pretty typical scenario for a lot of open source software. Updating dependencies is usually a pain.
My suggestion, before you try an upgrade, is to ensure you've got good test coverage so you'll see if anything gets broken. Also, make sure you do this on a separate branch from your main development, and try to get it done quickly before it divergest too much.
That said, unless there is something really compelling in the new generator, I probably wouldn't upgrade. But ymmv. I'd love to hear a more official response though too.
I try to update my app, runing the updated generator on my sources. I juste broke everything, too much diff, too complicated. (no problem here I'm using git).
My recommendation is to scaffold a new project using the updated generator then to manually copy my app into the new project. easier I guess
Perhaps you could scaffold the site with the old generator (the one you're currently on) and then a separate one with the updates. Then diff it?
@puneetagg Got it!!
Hi everyone, quick question. I just started with gulp-angular but Foundation is not working
You can fix it too. It will be a great exercise in understanding gulp better.
These kind of warnings happen often in the OSS world.
In a future update I'm sure they'll fix it. But I've found updating an already generated app to match the updates provided by an updated generator to be difficult.
example for creating a new templates and state?
Forkin autocorrect...
