Kyle Holmberg

@amitdahan instead of approvelisting specific other portals, we could adjust the ModalProvider like so: ``` { return !!target.closest(".react-aria-ModalOverlay"); }, }} > ``` thereby only closing the modal if the modal's...

Mental note for myself and maybe others: When this is available and working with inferred arguments we will be able to typecast return types depending on inferred generics 🥳 [demo...

This is very tricky. I wanted throw a suggestion out there: What if we split the `react-hookz/web` to have client-only and SSR-ready hooks? The type safety would be automatic and...

does something like this help? https://twitter.com/benlesh/status/1610298056540397568?s=46&t=Ar1ixjc9BhyFJS15ooM1Fg

I got hung up on the idea that we could conditionally use a different hook for https://github.com/react-hookz/web/issues/1000 and maybe define the initial value within _only_ `useEffect`, but that doesn't solve...

That still only adjusts the types, no? Won't all client-only users suffer from an extra render and bundled code?

hmmm the types don't solve the bigger DX problem which is that depending on your apps context, you'd need to provide arguments to certain hooks 100% of the time. Maybe...

lol yes it does 🤦🏼 ! sorry i was stuck thinking about that old PR and not this PR. then yes, i love it in conjunction with the TS idea....

@jasonwilliams do you know off the top of your head if there's an ideal extension version for other TS versions? I'll fix the lint errors :)

I ran the conversion script and had every one of my `QtCore.Signal()`s renamed correctly to `QtCore.pyqtSignal()`. Do you have more info on this?