Gary Burgess

Yeah, Real World Halogen uses `halogen-store` which does things that will trigger this situation.

I'll have to experiment a bit to check it out, as yeah it really would be nice if we could avoid the need for an iso here! If it doesn't...

Well, that's pretty much what the existing component model is for. :wink: The need for these `HalogenM` mapping functions is extremely uncommon - I've only used it once that I...

I'm not against it, and kinda anything `data-` is "standard" in the sense that it's backed by the `dataset` property in JS. The most pleasant interface for this might be...

Motivation... Going from this: ``` HH.div_ [ HH.button [ HE.onClick (HE.input ToggleState) ] [ HH.text "Close" ] , HH.text "Expanded" ] ``` To: ``` HH.div [ HE.onClick $ (HE.input ToggleState)...

You can end up with bugs because of disallowing shadowed warnings too - sometimes you reuse an `a` now where actually you meant to use `a1` or whatever, because you...

Fair enough! I had been intending to come back today and restate my dislike of this warning, since all the times I've had to work around it recently came back...

I don't really have enough information to answer this revised question, and it might even be an XY problem, so here's some stuff that may be relevant! To trigger an...

For this specific case you can use `Aff.delay` and `liftAff` within a `MonadAff` constrained `HalogenM`. In general, the pattern you mentioned with subscriptions is the intended way of doing this,...

I think multiple PRs is the only sensible way to approach it. We don't necessarily need an entry in the changelog for every single PR that adds docs to the...