Боремся со слишком большими Msg в Elm приложениях

Есть подозрение, что не уловил правильно суть статьи, но обычно (в Fable-Elmish по крайней мере) происходит построение дерева компонентов.  

module NestedComponentOne =
  module Types = 
   type Model = { Counter : int }
   type Msg = | Increment | Decremenet 
  module State = 
    let init () = { Counter = 0 }, Cmd.empty
    let update mode = function  //same as let update model msg = match msg with 
    | Icrement -> { model with Counter = model.Counter + 1 }
    | Decrement -> { model with Counter = model.Counter - 1 }
  module View =
   let view model dispatch = 
    div [ ] [
      h1 [] [ str "Counter" ]
      str <| sprintf "Counter value is %s" model.Counter
      button [ OnCick = fun _ -> despatch Increment ] [ str "Increment" ]
      button [ OnCick = fun _ -> despatch Decrement ] [ str "Decrement" ]
    ]
module NestedComponentTwo =
  ... Same
module RootComponent = 
  module Types =
    type Model = { SomeFields : SomeTypes, NestedComponentOneState: NestedComponentOne.Types.Model, NestedComponentTwoState : NestedComponentOne.Types.Model }
    type Msg = 
     | SomeMsgs of SomeTypes
     | NestedComponentOneMsg of NestedComponentOne.Types.Msg
     | NestedComponentTwoMsg of NestedComponentTwo.Types.Msg
  module State = 
     let init() = 
        {SomeFields = someFieldsInit() 
          NestedComponentOneState = NestedComponentOne.State.init()
          NestedComponentTwoState = NestedComponentTwo.State.init() }
    let update model = function //same as let update model msg = match msg with 
    | SomeMsg someMsg -> ...
    | NestedComponentOneMsg msg -> NestedComponentOneMsg.State.update model.NestedComponentOneState msg
    | NestedComponentTwoMsg msg -> NestedComponentTwoMsg.State.update model.NestedComponentTwoState msg
  module View =
    let root model dispatch =
      div [] [
         div [] [ str "ComponentOne"; NestedComponentOne.View.view model.NestedComponentOneState (NestedComponentOneMsg >> dispatch) ]
         div [] [ str "ComponentTwo"; NestedComponentTwo.View.view model.NestedComponentTwoState (NestedComponentTwoMsg >> dispatch) ]
      ]

как-то ну в разных файлах. в разных изолированных модулях. Это основная мысль