Mo Sattler

Hey @Helcaraxan, no worries, your work is appreciated either way!

Is there any workaround right now, where I can tell SWR that the data will be guaranteed to be defined, thanks to suspense and error boundaries?

@karol-majewski > If key can be falsy, then that implies data will sometimes be defined, sometimes not. I don't know the internals of useSWR, but couldn't one in principle use...

@karol-majewski > If customerId is nullish, the key is indeed a string, but the fetch call loses its meaning How so? Wouldn't the string evaluate to `'/customers/null'`, and SWR would...

> It is not, and that the reason why we have #1247 in the first place. I believe OP and myself are asking for the typing to properly reflect the...

same problem here

I have the same on iOS 13 🤔

> Something worth mentioning as well is the issue of using .orderBy() with .skip() and .take() which is also partially related to https://github.com/typeorm/typeorm/issues/747 Is there any way around this? Right...

Judging by the error log, this should be fixed by #9451

@olix0r yes - with types or integration tests.