At my company we have our own conventions, which are always good to have I think, even though the order doesn't really matter in this case.
This is our convention: 1) Core modules; 2) Public modules from elm-lang; 3) Other public modules; 4) Project modules. Anyway I see you mentioned List and Maybe. These are not necessary to import as they're part of the default imports <http://package.elm-lang.org/packages/elm-lang/core/latest/#default-imports> . On Friday, 2 September 2016 00:54:35 UTC+1, John Bugner wrote: > > Is there a "right" (de-jure or de-facto) way to order imports? If not, > then how do you order them? > > As I see it, there's two kinds of imports: > (1) local imports (Main, Engine, EnginePart, etc) > (2) and standard imports (List, Dict, Maybe, etc) > > I put the local imports first, then an empty line, then the standard > imports. > > And, is there a right way to order each import within its set? That is, > should one try to "logically" order them, like having 'import List' come > before 'import Array', because the former is more "basic" than the latter? > Or should they just be in alphabetical order? > > I prefer to logically order imports; I try to order them consistently in > every project, but it doesn't always happen. > > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
