JordanMartinez
JordanMartinez
So, here's a problem. A given field has the following pieces of state: - input - touched - output (i.e. the value when successfully validated) - dirty If I want...
Just FYI. `TimeHalogen` in the cookbook is using the `affEventSource`, so there's already an example for that.
This looks like it should be valid code to me. The problem is that the HookM code you define in the `parent` is run in the `child`. Thus, Halogen Hooks...
This bug should be renamed to something like, "Defining state-modifying `HookM` code in Component A and running it in Component B attempts to update Component B's state, not A."
> I’ll need to think a little on how to make this situation either not possible or at least not cause an exception due to the unsafe internal calls to...
So, how would we implement this if we weren't using Hooks and just using regular components? For example, I once tried using `HalogenM` as the action type. I believe I...
On second thought... this is actually problematic because the main code would then depend upon `purescript-spec` when only the test code should depend upon that... Hm...
The solution is basically another repo, but that's kind of a pain when the test code should be tightly coupled to this code here (such as if that specific function...
Sounds good to me!
I agree that we should wait until after Hooks have caught on and their tradeoffs are better known. As for the compiler errors... well... Having tried to implement some hooks...