https://training-course-material.com/index.php?action=history&feed=atom&title=AngularJS_Good_PracticesAngularJS Good Practices - Revision history2026-05-13T05:16:47ZRevision history for this page on the wikiMediaWiki 1.45.1https://training-course-material.com/index.php?title=AngularJS_Good_Practices&diff=37671&oldid=prevŁukasz Sokołowski: /* Bespoke agenda */2016-07-29T15:39:37Z<p><span class="autocomment">Bespoke agenda</span></p>
<p><b>New page</b></p><div>{{Draft}}<br />
{{Cat| Angular}}<br />
<!--<br />
{{Cat| JavaScript}}<br />
{{JavaScript Links}}<br />
--><br />
<br />
<br />
<slideshow style="nobleprog" headingmark="⌘" incmark="…" scaled="false" font="Trebuchet MS" ><br />
;title: AngularJS Good Practices<br />
;author: Lukasz Sokolowski (NobleProg Ltd)<br />
</slideshow><br />
<br />
== AngularJS Good Practices ==<br />
AngularJS Good Practices Training Materials<br />
<br />
{{Can I use your material}}<br />
<br />
== Intro ==<br />
Angular Bespoke Course Outline<br />
<br />
(Proposition of potential agenda, can be adjusted or extended)<br />
<br />
2 days training<br />
<br />
== Bespoke agenda ==<br />
<br />
* Avoiding major pitfalls of scaling an AngularJS app<br />
* Proper MVC directory structure<br />
* Writing Modules in a smarter way<br />
** Keeping the names consistent<br />
** Modularize the Header, Footer, Routes<br />
* Dependency injection and minifying the code<br />
** Global dependencies<br />
* Not-overusing Controllers<br />
** Syntax of 'controllerAs'<br />
** Using 'bindToController' in our Directives<br />
** Making 'ng-click' conditional<br />
* Factory vs Service<br />
** All providers are singletons<br />
* Utilizing browser extensions (Batarang, etc)<br />
* To many watchers and performance issues<br />
* Scoping<br />
** Write-only in the controllers<br />
** Read-only in the templates<br />
** Object in the scope instead of properties<br />
** Avoiding to shadow property of the parent '$scope' <br />
** Prototypical inheritance<br />
** Keeping scope uncluttered<br />
** How to talk with sibling objects<br />
* One-Time Binding<br />
* Not-manual testing<br />
** ngMock module<br />
** Protractor<br />
*** e2e tests with Jasmine<br />
*** '$digest' cycles<br />
** Karma<br />
*** How to easly close the feedback loop<br />
*** Run tests in parallel across different browsers<br />
*** Real world usage scenarios with different devices<br />
* Not-using jQuery<br />
** Change the way of thinking<br />
* Proper deploying<br />
** Facade to interact with servers<br />
*** Separation of server interaction and error handling from the model<br />
** Business logic in models<br />
** Configure providers before they are injected<br />
** Proper use of '$scope.$emit()' and '$scope.$broadcast'<br />
** Automating our workflow<br />
*** yo, grunt, bower<br />
* Agnular 1 vs Angular 2<br />
** Differences and similarities<br />
** Three ways: typescript, pure js, dart<br />
** Good practices in Angular 2<br />
** Upgrading from 1</div>Łukasz Sokołowski