Javascript to Elm

Route Components

Informações:

Sinopsis

From Page to Component Keeping our application modular, that means components Not your React Components Basically an Elm app that doesn’t expose a program Does not have a ‘main’ Rather it exposes it’s model/init, update, and view functions for other Elm modules to use Sound similar to life cycle methods? The modules state will be stored in the main with a little ‘m’ model expose Model, Msg, update, view and init doesn’t take () unit any more. Remember it’s called unit!!! Why doesn’t it? bc it’s not being invoked with the arguments that main would be, it’s exposing the other functions that it has. maybe? Gettin’ it done Storing an instance of the component’s model in Main’s model? Maybe not so much. The effect would be growing fields in the model for each and every component.