AngularJS Material: Material Design component library for AngularJS (1.x). Use angular/material2 channel for Angular Material (v2+).
hello all , anyone here ?
I set the
textarea attribute rows=5,but when I first load the page just one line on there
@siteshackinc hello
are you online ?
Hello, I’m new to Angular and I’m wondering how the app structure is set up. I’ve build applications in PHP where each ‘feature’ has it’s own file with it’s objects. But I don’t feel comfortable to create a new file for each factory and then include it in the index.html. What are your suggestions?
if you don't like adding them manually there are a lot of grunt/gulp modules to do it for you
maybe this style guide will help you https://github.com/johnpapa/angular-styleguide/blob/master/a1/README.md
It’s not about adding it manually. Generally it does not feel right to me to include a dozen of controllers, services and factories. But if that’s the way to go, I should get used to it ;-)
Thanks, will take a look at it.
it's generally considered better because individual bits of code are easier to test and maintain
also, when you get an error you can pinpoint it easier
because it occured in controller.js not in myapp.js line 2019 :)
I also recommend having a look at the angular yo generator and trying to understand how it's set up, I'm fairly new to angular myself and it's helped me out a lot https://github.com/yeoman/generator-angular
Already using yeoman. I understand their scaffolding. But was wondering if the same applied to services and factories :) For now I created the services and factories directories but while creating it and adding it to the index.html I was wondering if this was the way to go.
not because that guide said so, but because it's actually helpful :)
You could also give a look at using a loader (recommending SystemJS). Then your index is not bloated with js imports (and you still can maintain modularity for debugging)
can you tell me. over all design architecture of angular2 app
with directory structure
you could follow a component-per-folder architecture. Base your architecture on the ones from the angular 2 cli structure or whatever you think is best. Angular is component-oriented, so I guess grouping files by component has meaning.