News for hackers. Stuff that matters.
Re:Angular 2 Style Guide by pbreit on Thursday May 05, 2016 @11:40AM (#11637056)
Any tips for a mere mortal who looks at Angular and finds it incomprehensible? React? Vue.js? Or just stick to good ole Rails/Python for now?
Re:Angular 2 Style Guide by jashmenn on Thursday May 05, 2016 @11:52AM (#11637157)
One way to think about Angular is like this: Different modules on your page are broken down into components, which are like "regular" HTML tags except that they have JavaScript functionality attached to them. Your app is a tree of components.

React is great as well, but if you find Angular incomprehensible it's not clear you'll find React much easier.

One major difference between React and Angular is that the Angular community _tends_ to separate their templates from their "controller" code, whereas the React community _tends_ to intermix their templates with code ("PHP" style).

The result is that in Angular you have a few funny characters in your HTML to learn (e.g. `*ngFor="let foo in bar"` for looping) whereas in React you'll use JSX and use JavaScript for loops.

It's pretty clear to me that component-based webapps are here for the long haul. Even if WebComponents ends up being the future, the concepts you learn in using either Angular or React will be more-or-less transferrable.

It seems to me that Angular and React are becoming more similar over time. For typing, Angular uses TypeScript and React uses Flow. For data architecture, both communities are gravitating towards some sort of Flux (redux / ngrx). You can even use JSX in Angular if you want to.

Shameless plug: I've written a book on Angular 2 which talks through, step-by-step, how to understand Angular. The first chapter walks you through your first app and you can get it (for free) here: https://www.ng-book.com/2/

Re:Angular 2 Style Guide by nkw on Thursday May 05, 2016 @05:43PM (#11639868)
Lest anyone disregard the plug for the book because it comes from the author, I don't have any affiliation with the book or author, but can attest it is a very nice guide to Angular 2. During the alpha/beta process the angular developers have been making breaking API changes right and left (which is ok, they said they were going to during the development releases), but the ng-book 2 has been kept reasonably up to date through the process. I found it to be very helpful in getting a handle on angular2 -- much more so than all the sample projects or how-to pages mainly due to everyone preferring different tooling or build workflows which required more time to figure out what was going on there rather than learning the angular2 part. The book was much more pleasant to read and work through than all the how-to pages or seed projects on github. FWIW.
Re:Angular 2 Style Guide by nawitus on Thursday May 05, 2016 @12:44PM (#11637659)
Why use Angular 2 when you can use web components?
Re:Angular 2 Style Guide by zip1234 on Thursday May 05, 2016 @01:10PM (#11637925)
http://caniuse.com/#search=components

Because you can't practically use web components. Only Chrome and Opera support them. Angular2 has support down to IE 9.

Re:Angular 2 Style Guide by rictic on Thursday May 05, 2016 @01:39PM (#11638165)
The web components polyfills have support down to IE 10: https://github.com/webcomponents/webcomponentsjs
Re:Angular 2 Style Guide by pfooti on Thursday May 05, 2016 @01:56PM (#11638310)
Start with this: https://github.com/webcomponents/webcomponentsjs/issues/212

Which is why I stopped messing around with polymer. Basically adding the webcomponents polyfill to your DOM tree (because it touches so many things) breaks contenteditable in some weird ways. Which can be limiting to people who use rich text editors (many still decorate contenteditable divs) although iframe-wrapping the editor fixes the contenteditable breakage (at the expense of introducing other problems with extending your editor - try adding custom (say) atmention autocompletes to something in its own execution context).

Also, webcomponents have had some pretty major syntax changes over time, especially when it comes to shadow-piercing styling vs other styling selectors.

Ultimately, I'm looking forward to webcomponents. I can't wait to have proper namespaces and all that. In the short run, though, I've tried the webcomponents polyfill (I wrote a lot of polymer 0.X code for a webapp that I eventually ported to angular 1.x instead when the polymer 1.x syntax meant I'd have to rewrite a lot anyway), and it's not Enough.

Re:Angular 2 Style Guide by Touche on Thursday May 05, 2016 @01:45PM (#11638222)
Yeah but there's a separate "lite" version for a reason, Shadow DOM support requires wrapping nearly every DOM API. Web Components without Shadow DOM aren't that interesting.
Re:Angular 2 Style Guide by spriggan3 on Thursday May 05, 2016 @12:05PM (#11637276)
Try Vue.js frankly it has an excellent documentation.

And you'll get started in no time, no need for nodejs and zillion packages from npm, or even a cli tool and what not.

it's one file you drop into your html page. Vue.js explains clearly how you should build a Vue application and is honest about its potential limitations. There is no surprise nor magics. No IoC container forced on you if you're not into that kind of voodoo.

React is good too, I recommend either of them. I'd have recommended you Angular 1 3 years ago, now I can't, I have no idea if they'll stop developing that version at some point in time.

Re:Angular 2 Style Guide by devNoise on Thursday May 05, 2016 @04:56PM (#11639612)
Angular 1 is now up to 1.5.x and still has on going development. I think people have been scared away from learning Angular 1 because of the Angular 2 announcement. I'm trying to remember the details, but I believe support for Angular 1 will continue for a couple more years.
Re:Angular 2 Style Guide by Roboprog on Thursday May 05, 2016 @10:38PM (#11641319)
With any luck, Angular 1.x will be like Perl 5.x - still supported about 20 years later :-)

Did I just compare Angular 2 to Perl 6?

Alas, Angular 2 is threatening to actually roll out sooner rather than later.

Re:Angular 2 Style Guide by dceddia on Thursday May 05, 2016 @01:36PM (#11638140)
I'm a fan of React. Having used Angular 1.x for a few years professionally and spent some brief time with Angular 2, React seems like a much cleaner way to write view code.

The biggest hangup people seem to have at first is JSX ("HTML") mixed in with JS, and I had that worry too but it vanished as I spent more time with React.

It's just the view layer, and just a library, which can be a pro or con, depending on what you want from it.

Re:Angular 2 Style Guide by huskyr on Thursday May 05, 2016 @04:48PM (#11639554)
Vue is awesome. It has the templating parts of Angular 1 (which are quite nice), but it doesn't have the Java enterprise-like mishmash of services, factories, providers, modules and what have you not. I'm not sure if you should build a big application in Vue (maybe you should use React for that), but for a small-to-medium size app, Vue is an excellent choice.

Oh, and the documentation, a part so often neglected or written in a style that's for CS professors instead of mere mortals, is extensive, clearly written and full of examples. Lovely!

Re:Angular 2 Style Guide by posva on Friday May 06, 2016 @05:39AM (#11642727)
Actually Vue works as well or better than React for Big applications. You can handle application state with Vuex or other flux like implementation and even combine with a bigger backend
Re:Angular 2 Style Guide by ufmace on Thursday May 05, 2016 @01:26PM (#11638054)
My usual tip for getting into something that seems incomprehensible:

Just start building stuff in it. Start with Hello World or something else ridiculously simple. If it doesn't work, then debug and fix it until it does. If it works, then add some features until it stops working, then fix it. Repeat until it does something useful. Find some demo apps and examine them to give you some direction on how to do things. Work through any tutorials you find.

Angular 1 seems like a good starting place to me. It has some complexities, but it's one file to use and is all bare Javascript. You can at least get something simple working before you have to figure out how to set up build pipelines for Typescript or JSX or something. You can even do some useful stuff in it with no Javascript at all - the default form validation stuff is pretty nice.

Re:Angular 2 Style Guide by overcast on Thursday May 05, 2016 @12:02PM (#11637253)
Vue.js - MUCH easier to get started with, and will have most everything you need without the complexity of Angular.
Re:Angular 2 Style Guide by stephenhuey on Thursday May 05, 2016 @12:09PM (#11637309)
I've been finding the beta 1 version of Aurelia to be quite comprehensible and do prefer it to Angular by a long shot. They're getting ready for a release candidate now and the 1.0 version will be out within a few months.
Re:Angular 2 Style Guide by eliben on Thursday May 05, 2016 @01:12PM (#11637948)
Can you elaborate on how Rails/Python serves as an alternative to Angular?
Re:Angular 2 Style Guide by robotnoises on Thursday May 05, 2016 @01:20PM (#11638014)
I don't think they were implying it's an alternative, but rather very foreign-feeling.
Re:Angular 2 Style Guide by pbreit on Thursday May 05, 2016 @01:30PM (#11638083)
Both enable building web sites. Granted SPAs and MPAs are different, at the end of the day it's just building things for users.
Re:Angular 2 Style Guide by gremy0 on Thursday May 05, 2016 @11:25AM (#11636903)
"Write Angular 2 with style"

> Request javascript version

"This chapter is not yet available in JavaScript. We recommend reading the TypeScript version."

LOL

Re:Angular 2 Style Guide by spriggan3 on Thursday May 05, 2016 @11:32AM (#11636975)
Same with their tutorials on angular.io .

Angular2 is a framework build for Typescript and Dart, barely for Javascript and certainly not for ES5.

Re:Angular 2 Style Guide by zip1234 on Thursday May 05, 2016 @11:45AM (#11637105)
TypeScript is fantastic. Maybe it will be the undoing of Angular2 but I doubt it. The Angular2 team chose TypeScript because writing large applications using the limitations of ES5 is extremely difficult. TypeScript makes the task manageable and compiles back into ES5 (or whatever you want). The tooling is lightweight and freely available. Give it a try!
Re:Angular 2 Style Guide by spriggan3 on Thursday May 05, 2016 @11:53AM (#11637176)
Typescript isn't Javascript. I gave it a try already,for 2 years, and I used Angular 1 in production, I'm moving to something else like React or Vue.js, both supporting actual Javascript (even JSX isn't necessary). Good luck with your non standard syntax like decorators... Angular 1, despite its internal complexity, was just one file dropped in an html page and you're ready to go. There was nothing that mandated a complete rewrite with breaking APIs at first place. I complained to Igor 3 years ago about it. Well let's see how it goes.
Re:Angular 2 Style Guide by radicalbyte on Thursday May 05, 2016 @12:28PM (#11637507)
Typescript is ES with totally optional type information, which protects you from a whole lot of bugs and for javascript bad API design (i.e. horrors like APIs which return different types with different input).

I can understand that it feels strange, especially to someone who has had little exposure to languages outside of Javascript. However it is very much worth investing the time in learning it.

15 years ago I was making the same argument to Visual Basic developers about C#..

Re:Angular 2 Style Guide by gshulegaard on Thursday May 05, 2016 @01:34PM (#11638121)
I'm sorry but I will never use Angular 2.0 unless it can be used with straight JavaScript. I am a backend developer that, for personal projects, needs to do small amounts of front-end work. Anything that potentially increases complexity or involves a redundant learning curve (learning yet another _imperative_ language that compiles into JavaScript anyway) is not something I am going to invest time in.

It's a shame too, I was a pretty big Angular fan. I used Angular, Ember, and even React and for several reasons I ended up settling on Angular as my favorite SPA framework (back in 2014 and 2015). Back when they announced Angular 2.0 would be TypeScript based, I felt like it was a mistake and that feeling has only gotten stronger as TypeScript has continued to fall behind EMCAScript (http://kangax.github.io/compat-table/es6/).

If TypeScript adopts compilation down to WebAssembly, that would be a reason to learn it/give Angular 2.0 a chance for me, but until then I will stick to Angular 1.0 or move towards React for my next project...which is a shame because I really don't like Reacts focus on the V of MVC. Maybe I will go back and check on Ember, but I wasn't a fan of it's tight binding of Models to Views (sometimes I just need a VC or a V and not a full MVC)...but maybe it has changed.

Re:Angular 2 Style Guide by squeaky-clean on Thursday May 05, 2016 @02:31PM (#11638615)
> I'm sorry but I will never use Angular 2.0 unless it can be used with straight JavaScript.

It can. Typescript is just optional information added to your Javascript. All Javascript is 100% compatible TypeScript. You can use TS extensions anywhere you like, your whole codebase, only certain function APIs, or nowhere at all.

Re:Angular 2 Style Guide by Roboprog on Thursday May 05, 2016 @11:09PM (#11641419)
Ugh, I'm tired of mandatory "OOP for dummies" a la Java (and C# to a lesser degree). I've been programming since the early 80s, and I have been exposed to more than just Javascript, or Java/C# for that matter. (BASIC, Fortran, Pascal, Lisp, some assembler, xBASE, C, some C++, Shell, Perl, Java, C#, Ruby, Javascript, some Python, some Objective C, some Scala, Groovy and smatterings of other proprietary / DSLs)

My first job in the mid 80s was in a language with runtime typing. My experience is that "strong" (compile/parse time) typing is not the panacea that many say it is. I've seen far more damage caused by C style "operator precedence stew" issues (vs Lisp style all funcs w/ parens). It's like the Type Police have to punish us for the dark era of C/++ Play-dough Pumper byte molding the industry had to put itself through in the 90s.

In fact, I would much rather see a language that forced modules/data/functions to be flagged which were not immutable/idempotent (which should be an enforced default), rather than an even-trade-at-best static type feature. Yes, that means your "main" would be flagged as "dirty", so it could do I/O, but your library modules (lang; 3rd party; app) would mostly be pure functions.

Anyway, I much prefer dynamic (runtime) types and FP with an occasional dash of OOP style Javascript to the "Let's be like Java!" cult. As Douglas Crockford likes to say "Those people will go to their graves, never knowing how miserable they are". Ironic, considering how the coming holy grail of ADTs/Objects was beaten into us in Uni in the 80s, and FP all but ignored.

Re:Angular 2 Style Guide by Roboprog on Thursday May 05, 2016 @11:26PM (#11641479)
As long as I'm peeving at length about the Java meme plague, I wish the whole MashedUpCamelCraps identifier style would just die, already, vs you_can_skim_this style.
Re:Angular 2 Style Guide by Touche on Thursday May 05, 2016 @01:34PM (#11638120)
You're wrong, there are various other differences. Some of what TypeScript implements isn't supported by JavaScript yet (like import/export for example). It's very much a different language, which is fine, but it is annoying to constantly hear "it's just JS with optional types".
Re:Angular 2 Style Guide by pfooti on Thursday May 05, 2016 @01:48PM (#11638247)
I use import / export in my regular javascript. I just use babel and browserify for it. I am sure that there are typescript language features that aren't "just optional types", but I don't think import / export is so far outside the normal ES/next kind of norm that you'd call it some kind of MSbomination.
Re:Angular 2 Style Guide by Touche on Friday May 06, 2016 @11:15AM (#11644518)
Babel is not "regular JavaScript", your import/export statements won't work when browsers and Node support them (you are required to include the .js extension and Babel doesn't enforce that). Babel also supports things like JSX and Flow.
Re:Angular 2 Style Guide by plexicle on Thursday May 05, 2016 @01:40PM (#11638183)
"both supporting actual Javascript (even JSX isn't necessary)."

Oh, come on now. If JSX isn't necessary, then neither is TypeScript. Have you tried writing React components without JSX? Angular2 in ES5 is saner.

I get that neither is ideal, but let's be real here.

Re:Angular 2 Style Guide by Roboprog on Thursday May 05, 2016 @10:46PM (#11641348)
I loved the way you could start with a static HTML mockup with Angular, then add the boilerplate in a single .js file, then define a simple data model in the js, slap in some curly braces and ng-model attributes hit "reload" and try it out, lather, rinse, repeat -- all without any build (transpile, concat) step.

Angular 2 looks like a JEE "inspired" nightmare.

Re:Angular 2 Style Guide by Roboprog on Thursday May 05, 2016 @11:11PM (#11641425)
Of course, by the time you get to event handlers and REST calls, you need a back end, but you could mock up an awful lot in 1.x without ever worrying about a "build".
Re:Angular 2 Style Guide by AshleyGrant on Thursday May 05, 2016 @02:21PM (#11638542)
"non standard syntax like decorators"????

decorators are a TC39 proposal from Yehuda Katz and Jonathan Turner...

Re:Angular 2 Style Guide by spriggan3 on Thursday May 05, 2016 @04:01PM (#11639250)
proposal =/= in the spec. Typescript used to have a module implementation that was not compatible with ES6 modules. Guess what happened for Typescript developers.
Re:Angular 2 Style Guide by Roboprog on Thursday May 05, 2016 @10:42PM (#11641328)
Remember GWT? We were all going to write client-side widgets in Java.

Turned out, that was a nuisance.

Re:Angular 2 Style Guide by paulddraper on Thursday May 05, 2016 @04:34PM (#11639468)
I'm using it with ES5 only.
Re:Angular 2 Style Guide by spriggan3 on Friday May 06, 2016 @11:37AM (#11644664)
Why don't you post some snippets or gists so that everybody can get a mesure of what a large app looks like with Angular 2 ? that's right, it is not designed to be used with ES5.
Re:Angular 2 Style Guide by paulddraper on Sunday May 08, 2016 @03:00AM (#11653003)
Well, the project is not open source :(
Re:Angular 2 Style Guide by Roboprog on Thursday May 05, 2016 @10:33PM (#11641297)
You should put up some examples on github and post a link.

TIA

Re:Angular 2 Style Guide by ben_jones on Thursday May 05, 2016 @01:57PM (#11638328)
People have brought it up but I feel the need to drive it home: while Typescript is amazing and, when used correctly, can allow more expressive and bug-free code then es5, adoption will suffer greatly and has the potential to detract from the overall success of Angular 2.0.
Re:Angular 2 Style Guide by rubber_duck on Thursday May 05, 2016 @02:21PM (#11638545)
Typescript is the feature of Angular 2.0 for me

There are plenty of ES5 frameworks out there - the biggest value proposition Angular 2 brings for me is that it's built with typescript from the start and it leverages all of it's features (ie. modern OO tooling that comes with languages like C# and a language that feels familiar to C#/Java devs) and builds a GUI framework on top of it that works in the browser.

Without being native TS Angular 2 would have very low appeal to me.

Re:Angular 2 Style Guide by Roboprog on Friday May 06, 2016 @12:41PM (#11645097)
You know, there are some of us who like the fact that Javascript is a dynamic language that supports functional programming (FP) style.

For us, "being like Java" is not a plus. My IDE already does a pretty good job at type inference while I am editing, as well as displaying the comments about each symbol as I click on it.

Re:Angular 2 Style Guide by netinstructions on Thursday May 05, 2016 @12:01PM (#11637234)
You could also run the Codelyzer (A set of tslint rules for static code analysis of Angular 2 TypeScript projects) with the recommended configuration to match this style guide.

https://github.com/mgechev/codelyzer

Re:Angular 2 Style Guide by bshimmin on Thursday May 05, 2016 @12:37PM (#11637595)
I don't much care for Angular, but this is some seriously beautiful documentation.
Re:Angular 2 Style Guide by GnarlyWhale on Thursday May 05, 2016 @11:11AM (#11636786)
Happy to see the pace at which the angular team is updating their support docs now that they are in beta.
Re:Angular 2 Style Guide by lobo_tuerto on Thursday May 05, 2016 @11:19AM (#11636857)
You mean now that they are in release candidate! ;)
Re:Angular 2 Style Guide by chvid on Thursday May 05, 2016 @02:17PM (#11638510)
So Angular is all TypeScript now?! With a recommendation for Microsoft's editor at the end of the article.

Anyways - it seems like a set of reasonable conventions; Java/C# programmers should feel right at home.

The only thing that sticks out is the file name convention. If you only have one thing pr. class then why not use name as it is directly in the file name? (HeroComponent.ts instead of hero.component.ts)

Re:Angular 2 Style Guide by r0m4n0 on Thursday May 05, 2016 @12:41PM (#11637634)
I'm really excited to see there will be an official style guide that was truly lacking in v1.x

Having worked on various teams (now we follow https://github.com/johnpapa/angular-styleguide), its truly a maintenance nightmare without a verbose Angular style guide for reference.

Re:Angular 2 Style Guide by andrewstuart2 on Thursday May 05, 2016 @01:00PM (#11637814)
I'd highly recommend using something like eslint, which can be integrated into editors and CI flows to assist with most of the style guide choices (at least the never/always kind) that your organization makes.

Use some style guide as a base and then agree on your own internal exceptions/additions as a team, then just implement those rules, and eslint can let you know when you've forgotten something.

Personally, I find the editor (via Syntastic in vim) integration most helpful since it's more of a warning and not an overbearing release gate.

Re:Angular 2 Style Guide by r0m4n0 on Friday May 06, 2016 @02:38PM (#11645806)
Yep, well aware and utilize plenty of linting. Javascript style is one thing, Angular (amongst other frameworks) leave much room for different styles of structure, modularization, dos/don'ts. It's important to agree on one set of framework styles as a team otherwise consistency of patterns could be a nightmare. Having an official style guide (which didn't exist with Angular 1) simplifies this...
Re:Angular 2 Style Guide by lobo_tuerto on Thursday May 05, 2016 @12:59PM (#11637801)
Lacking how? John Papa's style guide has been around for some time, and it's endorsed by the Angular team.

He is in charge of the Angular 2 style guide too. I bet he will do a good job with this one too.

Re:Angular 2 Style Guide by devNoise on Thursday May 05, 2016 @05:07PM (#11639669)
Just to follow up. John Papa's original style guide was create after he had experience with building Angular 1 apps and got feedback from other developers. An Angular 2 style guide can't be fully formed right now because no one really knows what all of the best practices are yet. As all of us get more experience using Angular 2, the style guide will get better.
Re:Angular 2 Style Guide by r0m4n0 on Friday May 06, 2016 @02:34PM (#11645778)
Endorsed vs official are two different things. There are many style guides (and some don't agree with the entire John Papa style guide leaving room for reasonable debate)
Re:Angular 2 Style Guide by robotnoises on Thursday May 05, 2016 @01:10PM (#11637935)
From: https://angular.io/styleguide#!#style-03-03

> Consider naming an interface without an I prefix.

They give the same recommendation in the Typescript style guide, but I still don't understand why.

Re:Angular 2 Style Guide by netinstructions on Thursday May 05, 2016 @01:18PM (#11637993)
This is a common discussion I see on the internet[0][1][2][3]. Paraphrased below

You shouldn't need to know whether the client is using an interface or an implementation class. List represents a list, and a User represents a user - not an IUser. Another problem with using I, is that (oddly) we use it to communication the implementation decision of using an interface. Usually we don't want implementation decisions expressed so loudly, because that makes them hard to change.

[0]http://programmers.stackexchange.com/questions/117348/should...

[1]http://stackoverflow.com/questions/541912/interface-naming-i...

[2]http://stackoverflow.com/questions/5816951/prefixing-interfa...

[3]https://blogs.msdn.microsoft.com/brada/2004/02/03/why-do-int...

Re:Angular 2 Style Guide by robotnoises on Thursday May 05, 2016 @01:31PM (#11638091)
Excellent reply, thank you.

To me, it still seems more about people's gripe over the very existence of interfaces.

If anything, using IUser in lieu of User is a pretty clear signal to, say, an uninitiated developer, that you shouldn't be attempting to create an instance of "IUser."

Re:Angular 2 Style Guide by teen on Thursday May 05, 2016 @05:48PM (#11639898)
In the first suggestion they suggest breaking up a component into its own folder. That quickly becomes a completely mess imo. Better to prefix the filename with the component (hero.service.js) and leave everything in the same directory.
Re:Angular 2 Style Guide by EugeneOZ on Thursday May 05, 2016 @06:14PM (#11640069)
If each component have 3 files, how can 10 folders (with 3 files inside) be a more mess than list of 30 files with prefixes?
Re:Angular 2 Style Guide by abiox on Thursday May 05, 2016 @12:36PM (#11637588)
does angular2 support preloading data/setting initial-state, such as by server-side templating?

if not, can i run angular2 in, say, nashorn to generate view data?

Re:Angular 2 Style Guide by kabes on Thursday May 05, 2016 @02:46PM (#11638742)
Yes, it's called 'angular universal'. Here's a talk of ng-conf: https://www.youtube.com/watch?v=TCj_oC3m6_U&index=5&list=PLO...
Re:Angular 2 Style Guide by Roboprog on Thursday May 05, 2016 @11:27PM (#11641482)
How many symbols are all of those .ts files going to put into the global namespace?
Re:Angular 2 Style Guide by scriby on Thursday May 05, 2016 @11:43PM (#11641541)
The .ts files will be compiled to AMD modules, so none of the declarations will be in the global scope.
Re:Angular 2 Style Guide by Roboprog on Friday May 06, 2016 @11:48AM (#11644740)
Thanks, I had not seen that before. Interesting trick: Call a "registration" function with a string array (of dependencies) and an anonymous function (IIFE) with parameters for each dependency which the registration function injects. Thus, the dependencies are accessed as closures over the outermost func's params, rather than as globals.

E.g. -

    define( [ 'jQuery' ], function ( $ ) { ... return { ... } } )
where the 1st elipses are all the private/setup code, and the second elipses are whatever methods/properties the module exports. (this dummy only wants jQuery, but the list can be longer)
Re:Angular 2 Style Guide by meeper16 on Thursday May 05, 2016 @11:34AM (#11636995)
Looking forward to forced indentation + javascript.
Re:Angular 2 Style Guide by ihsw on Thursday May 05, 2016 @11:43AM (#11637082)
It already is forced -- see: ESLint.
Re:Angular 2 Style Guide by vmateixeira on Friday May 06, 2016 @04:00AM (#11642410)
Anyone getting along with angular forms?