eh-dub

export type CountryCode =
  | "AF"
  | "AX"
  | "AL"
  | "DZ"
  | "AS"
  | "AD"
  | "AO"
  | "AI"
  | "AQ"

eh-dub

// in $PROJECT_ROOT/typings/@sapper
declare module '@sapper/app' {
  // from sapper/runtime/src/app/types.ts
  // sapper doesn't export its types yet
  interface Redirect {
      statusCode: number
      location: string
  }
  // end

eh-dub

Managing Complexity in Elm

I have been writing Elm code for a recent project. It is great at the start, but then the model gets larger and complexity creeps in. Files grow over 100 lines in length. That's a sign of trouble.

The official Elm Guide offers a few words about reuse and it is worth giving it a read. However, it is anchored in reuse of view code and does not offer any information about decomposing the Update and Model monoliths.

How to best dissolve my ever expanding Update.elm and Model.elm?

Update and Model

eh-dub

module Update exposing (update)