Joe Pea
Joe Pea
Yeah perhaps `true` would make more sense here, to be consistent with ``
@vparpoil reproduce with this one: ```sh [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] # without this commented out, you will get the error # [email protected]...
Hmm yeah, don't want duplicates. Maybe this is a more generic problem: instead of one-off solutions, maybe `npmDepends` needs to be updated so it handles this case in a way...
Okay, I made a small reproduction: https://playground.solidjs.com/anonymous/1995cd34-a712-44d3-9b02-9a4871a062a9
> This is a tough one, I have not been keen to touch `html` because there's too much string manipulation for my taste. 👍
> the syntax is different `` vs `` @titoBouzout I love the new Syntax. Much easier to use. > it's nice, but it's slow. I'd rather have something that works...
Hey @alphabetabc, I moved your changes into this branch in the main repo, so that I could get the tests to run. Some of the tests are failing with this...
I don't understand what you're describing up above, but Solid's upcoming signals update "async signals" are supported by having signals that are not yet resolved throw a special error (React...
> Because in those situations generally the unit of computation is always synchronous conceptually (even if the value isn't available yet). It's clever that it *looks* sync, but I prefer...
> Without using useEffect, you can create a helper function like this: > > ```ts > //null, means calculating the value > const asyncComputed = ( > ``` That doesn't...