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
moduleMainwhereimportPreludeimportEffect (Effect)
importFlame.Application.NoEffects (mount_)
importFlame.Html.ElementasHEimportFlame.Types (Html, Subscription)
importFlame.Html.AttributeasHAimportFlame (QuerySelector(..))
typeModel=InttypeMessage=Model->Modelinit::Model
init = 0subscribe::Array (SubscriptionMessage)
subscribe = []view::Model->HtmlMessage
view model = HE.button [HA.onClick ((+) 1)] (show model)
update::Model->Message->Model
update model message = message model
main::EffectUnit
main = do
mount_ (QuerySelector"body") { init, subscribe, view, update}
I get that the point of messages is to limit the type of mutations one can do on the model. But I was playing around with that, since it allows me to try some things faster while i decide how to structure the state and its mutations. Trying this however fails, and when the button is clicked the following error is logged
caught TypeError: h(...) is not a function
at F.runHandlers (index.js:2273:51)
at F.runEvent (index.js:2264:14)
Is this known?
The text was updated successfully, but these errors were encountered:
Thanks for bringing this up. I don't think anyone have tried to use a function as message type. It should be possible to patch but were you thinking of using function just to avoid defining sum types?
I mean, I do think using a Sum type is the better choice. I just was playing around mostly, since i'm currently learning purescript and flame. And wanted to edit the model loosely cause i didn't want to plan ahead for the most part and discovered the bug. If it helps, wrapping the function in another type solves it. And sending a message with send doesn't trigger it either. I am just opening the issue for robustness' sake mostly
The minimal reproducible example would be this.
I get that the point of messages is to limit the type of mutations one can do on the model. But I was playing around with that, since it allows me to try some things faster while i decide how to structure the state and its mutations. Trying this however fails, and when the button is clicked the following error is logged
Is this known?
The text was updated successfully, but these errors were encountered: