AppObject is the object you should return from your side effect functions (init, update) in your components.

• appData refers to the model you want to be global to your application. This model is usualy stored in your root state
• appMsg refers to the msg type you want to be global to your application. This msg is usually handle in your root update function
• model refers to the model of your current component
• msg refers to the msg type of your current component

I suggest your create a module that defines your appData model and your appMsg message type, and you define a type alias of your own AppObject with the appData and appMsg set :

type alias MyAppObject model msg =
    AppObject.AppObject Data AppMsg model msg


type alias Data =
    { isModalOpen : Bool
    }


type AppMsg
    = ToggleModal Bool

Creates a new AppObject from the appData and your component's model

Adds a new component's command to this AppObject

Adds a new global command to this AppObject

Maps your AppObject to change the types of appData, appMsg, model and msg

Maps only your appData

Maps only your appMsg

Maps only your model

Maps only your msg

Merges 2 AppObjects together. You provide the functions used to:

• merge the model
• merge the appData
• map the msg
• map the appMsg

Reducer that allows you to update or create an AppObject for each element of a list

Allows you to create a new AppObject from an existing one, using the appData and the model. The new Cmd appMsg and Cmd msg will be batched to the existing ones

Executes your AppObject. That means that you will create a ( model, Cmd msg ) tuple from an AppObject, this allows you to run your side effects and model updates in your root update and init functions