@romain-deneau.bsky.social
I'm interested, for December the 20th 🙏
November 14, 2025 at 5:49 AM
I'm interested, for December the 20th 🙏
Thank you for the feedback 🙏
October 14, 2025 at 5:26 AM
Thank you for the feedback 🙏
On my side, I prefer to see all the features directly with both the Model and the Msgs, without having to look at the implementation in the view and update functions. It's the beauty and the power of Elmish / MVU pattern. It's pragmatic too, based on another tradeoff.
October 14, 2025 at 5:25 AM
On my side, I prefer to see all the features directly with both the Model and the Msgs, without having to look at the implementation in the view and update functions. It's the beauty and the power of Elmish / MVU pattern. It's pragmatic too, based on another tradeoff.
Yes, I like the flexibility that offers Elmish. Your approach is interesting, using the Cmds for effects including UI ones, as long as it's a deliberate choice. For instance, if we need to test the business rules regarding the display of such messages, it's more convenient with the Model.
October 14, 2025 at 5:13 AM
Yes, I like the flexibility that offers Elmish. Your approach is interesting, using the Cmds for effects including UI ones, as long as it's a deliberate choice. For instance, if we need to test the business rules regarding the display of such messages, it's more convenient with the Model.
It's more aligned with the Elmish philosopy. What do think?
October 13, 2025 at 9:34 AM
It's more aligned with the Elmish philosopy. What do think?
Thx for the tips. I like the 1st one: ServerApi.mkDefault().
On my side, I do nothing related to the UI in the update function. I only use the Model for that. For instance, to trigger `Toastify.error`, I would have an optional Error in the Model.
On my side, I do nothing related to the UI in the update function. I only use the Model for that. For instance, to trigger `Toastify.error`, I would have an optional Error in the Model.
October 13, 2025 at 9:34 AM
Thx for the tips. I like the 1st one: ServerApi.mkDefault().
On my side, I do nothing related to the UI in the update function. I only use the Model for that. For instance, to trigger `Toastify.error`, I would have an optional Error in the Model.
On my side, I do nothing related to the UI in the update function. I only use the Model for that. For instance, to trigger `Toastify.error`, I would have an optional Error in the Model.