You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think using this pattern doesn't make it obvious for how users might expand on the example. If a user does decide to use a struct as their model, the code written in update and view also need to updated, while not always obvious. For example, a user might try to do this:
...and not realize that you can't use model in this way as you could when it was a type alias. I think more modular the first example is the best it is for the user experience.
The text was updated successfully, but these errors were encountered:
If I remember correctly, you are not the first one who suggested this change and I think it's a good idea. The type alias was inspired by the Elm Counter / Buttons.
However together with the change in this repo we should update the example and related docs also in:
@MartinKavik The 3 referenced areas have been updated. However, there is (at least) one separate page on the website for the Model that I haven't updated yet. Will take a shot at it shortly.
I think using this pattern doesn't make it obvious for how users might expand on the example. If a user does decide to use a struct as their model, the code written in update and view also need to updated, while not always obvious. For example, a user might try to do this:
...and not realize that you can't use model in this way as you could when it was a type alias. I think more modular the first example is the best it is for the user experience.
The text was updated successfully, but these errors were encountered: