That's funny, I think I've internalized this unexpected behavior so much that it didn't even occur to me that anything wrapped in that function could affect the type checker 😅

Maybe you meant to throw if value === 0 instead of !==

Haven’t you type narrowed that the value is zero past the throw?

The features are awesome. I love it, and my four year old is super into Transformers and Lego. But $190 frankly is bullshit! 😅 Demand commands the market price and all that and I know there are even more ludicrous sets, but I'll never pay that much.

190 USD... 😞

Just don’t fly over Central Park that shit is the worst. Nothing like a nice quiet walk ruined by a loud ass chopper hovering overhead.

Looking good! Will it support multi-select?

Just saw the new query/form example and wanted to say thank you! Very helpful.

Thanks Corbin I will try out that refetch example! Here is a discussion post I made with this suggestion a little while ago: github.com/TanStack/for...

A pattern we run into is with a “live” form that persists / remains open after save. Could we see an example where a query is invalidated on successful mutation (or imperatively set the query value) and the form state is reset with the new query result value in a clean state?

Would be helpful to see a react query example that showed a deeper integration. The existing “query integration” example seems not to show an actual integration, just that you can initialize undefined until your initial values are ready, and on submit you can call an asynchronous function.

Seeing that linting warning might push someone to swap between `useLayoutEffect` and `useEffect` to avoid both that and the "useLayoutEffect won't run on the server" message!

Excellent read! I have a question about Shane's implementation where the body of the custom hook includes:

```js
if (typeof document === "undefined") return;

useLayoutEffect(...args);
```

Wouldn't this conditional return of useLayoutEffect violate the rules of hooks?