The naming of two states and events in the demo ist not optimal. The following two values are defined in app-ui-login-model.js: "state:button-enabled" and "event:button-clicked".
As this file represents the model, it should be independent from any view realizing it - so the name "button" should not be used. A view could realize the Login activation with another ui element like a slider.
I propose "state:login-enabled" and "event:login-activated" as better names.
The naming of two states and events in the demo ist not optimal. The following two values are defined in app-ui-login-model.js: "state:button-enabled" and "event:button-clicked".
As this file represents the model, it should be independent from any view realizing it - so the name "button" should not be used. A view could realize the Login activation with another ui element like a slider.
I propose "state:login-enabled" and "event:login-activated" as better names.