Dav
I was already casting my response like so: ```ts const response = await fetch(url, { headers }); const json: MySpecialResponseType = await response.json(); ``` Since `any` is pretty much useless...
If the type doesn't matter to you then let it stay as unknown. But the fact remains, there is no way to be absolutely sure what the server returned at...
> I even tried doing this but I just ended up with tons of useless interfaces that mean absolutely nothing and present no advantage at all I see your issue...
When you called .json you got a type of `any`, at some point you must have type narrowed or casted it to something useful you want to use. ```ts const...
Absolutely, I was trying to use it like this and was surprised it wasn't possible.
Can we get this merged?
I've been recently trying to write tests using react testing library and it seems impossible to get the bottom sheet to "be visible" to jsdom. Seeing as most of my...
There is a workaround @rjohnsonbade-dcs , I found that you can mock 'react-spring' and bottom sheet relies on that for calculations. Something similar to this should get you 90% of...
I would hope that this feature falls under the "typescript" project on the roadmap @mikehardy Converting a project from web to native means it isn't as straightforward as I hoped...
@haeniya I just used a TS cast to the type I know it should be (although it should be safer to do as @jthoward64 suggests to have a runtime check...