I do not believe there are any best practices - Google turns up nothing and
if it's not in Google, it doesn't exist (a little humor there). The
ordering of the imports has no effect on the application and, IMO, it does
not increase readability/understanding when you enforce an arbitrary sort
on the imports.
The only thing I do is split the imports into two groups, placing external
modules first like so:
import {Injectable, provide} from '@angular/core';
import {Http} from '@angular/http';
import {MyComponent} from './my-component';
On Thu, Jul 21, 2016 at 9:40 AM, Supun Budhajeewa <[email protected]>
wrote:
> On Thursday, July 21, 2016 at 7:03:57 PM UTC+5:30, Lucas Lacroix wrote:
>>
>> You can order the imports in any way you want.
>>
>
> Please note that I am looking for "best practices".
>
> --
> You received this message because you are subscribed to the Google Groups
> "AngularJS" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/angular.
> For more options, visit https://groups.google.com/d/optout.
>
--
Lucas Lacroix
Computer Scientist
System Technology Division, MEDITECH <http://ehr.meditech.com>
781-774-2293
--
You received this message because you are subscribed to the Google Groups
"AngularJS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/angular.
For more options, visit https://groups.google.com/d/optout.
