Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Mike Sigsworth
    @mikesigs
    _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?
    Mike Sigsworth
    @mikesigs
    It looks you can either get rid of the second beforeEachand the let userOptions statement, or replace the userOptions passed into each arrow function with ()
    Justin
    @JRhyne
    Ahh gotcha. Thank a lot man!
    kingdeejaymes
    @kingdeejaymes
    Hi, is it possible to change the default port to listen to "localhost:8000" instead of "localhost:3000"? thanks!
    Rodnei Couto
    @rodneicouto
    There was a mode to escape a config.js file in the build process? me desire is maintaining a untouchable file with name src/config.js to the support configure some properties in production, together with index.html.
    David
    @MoxFulder
    is it a good practice to upgrade the generated files to a new version (scaffolding again the app on existing sources) or not ?
    (using a newer generator version)
    Mike Sigsworth
    @mikesigs
    I'm not an expert, but I'll give you an answer based on my experience.
    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.
    David
    @MoxFulder
    @mikesigs thank you for your answer
    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
    Mike Sigsworth
    @mikesigs
    @MoxFulder That's probably the best idea.
    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?
    David
    @MoxFulder
    anyone here is using a theme ? Like a theme sold on themeforest ? I would like to know if someone has advices about chosing a theme which is a good choice to work with
    Mike Sigsworth
    @mikesigs
    Puneet Aggarwal
    @puneetagg
    Hi..Can any body tell me whats the significance of export keyword before function in JS generated by yeoman?
    Puneet Aggarwal
    @puneetagg
    This message was deleted
    @puneetagg Got it!!
    Kevin Sumang
    @kvnsmng
    This message was deleted
    Hi everyone, quick question. I just started with gulp-angular but Foundation is not working
    Puneet Aggarwal
    @puneetagg
    Hi... I am new with Gulp. While using the generator, I am getting the warning:
    npm WARN deprecated gulp-minify-css@1.2.3: Please use gulp-cssnano instead.
    Do I need to change somewhere in yeoman or project's package.json or something else?
    Mike Sigsworth
    @mikesigs
    It's just a warning. You can leave it as it is and everything will be fine.
    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.
    Puneet Aggarwal
    @puneetagg
    @mikesigs Thanks for the reply. I think issue is with generator as its using the deprecated packages. Also what's OSS?
    Mike Sigsworth
    @mikesigs
    Yes. The generator is relying on an old package. It happens. OSS = Open Source Software
    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.
    Puneet Aggarwal
    @puneetagg
    @mikesigs Ok. Thanks!!
    Maker Su
    @makersu
    hi, how to add a page after yo gulp-angular?
    example for creating a new templates and state?
    Matthieu Lux
    @Swiip
    hi, there is no generators after the first yo gulp-angular
    Maker Su
    @makersu
    update index.route.js and mkdir a folder for a new menu?
    Matthieu Lux
    @Swiip
    yep for example, you also can create a new something.route.js
    Maker Su
    @makersu
    thanks, any example used gulp-angular?
    Mike Sigsworth
    @mikesigs
    @makersu you could always girl the generator on guthub and customize it there.
    Mike Sigsworth
    @mikesigs
    Fork. Not girl.
    Forkin autocorrect...
    Nikita Buyevich
    @nikitabuyevich
    Hi, I have a question with how I can launch js files after it loads the angular views instead of before. Because I'm trying to access the DOM with javascript but it doesn't exist yet (because it runs the javascript first, before the angular views)
    Nikita Buyevich
    @nikitabuyevich

    for example if I want to get access to,

    document.querySelector('.some-class-name').clientHeight;

    I can't do that because the class hasn't been loaded yet because this script will run before the angular directive view loads.

    Mike Sigsworth
    @mikesigs
    You should read up on directives. This is more of a general angular question, and not really specific to this generator. Perhaps try Stack Overflow.
    Nikita Buyevich
    @nikitabuyevich
    Yeah I did, there's the compile command which will run the code after the directory is finished rendering but I want to try and get the DOM of the entire main.html file which doesn't use a directory, it uses stateProvider, is there a similar command but for the main.html file?
    Mike Sigsworth
    @mikesigs
    Build a directive and put it on the body beside the ng-app directive? What you're maybe trying to do sounds like an anti-pattern though.
    Nikita Buyevich
    @nikitabuyevich
    Hmm than what would be the best way to work with the DOM using the set up that this generator has? Because I'm trying to stick to that structure of having directives in the main.html and outputting the main.html in the index.html