Tests are a good test of how usable your code is in other contexts.

I've got to feel sorry for the devs who write code who later have a consultant come in and put them on blast on twitter.

Whaaaat. Github is 100% good, no notes

wtf. 😳

You can do component tests with real browser tools like Cypress though. And these are arguably more useful than something like RTL where you're having to mock some browser APIs, and likely getting it wrong.

I still use it. It's a good FTP client.

users, then we can widen that label type to `label?: string | (user: User) => string`. The old code works fine, but we've got our new improved functionality too.

No... widening types is a pretty standard pattern for extending code functionality without making breaking changes. For example, let's say we had a function `renderUsers(users: User[], label?: string)` and we realise 'oops, we want to dynamically determine the label based on...

Oh FFS. What's even the point of having DMs open?

Accompanying blog post for my talk at @melbjs_ tomorrow night: blacksheepcode.com/posts/tes…

Use a form.

Edit: *`qc.getQueryData`

(probably my biggest gripe about rq, is the lack of type safety with getQueryData, setQueryData, but I'll live with it)

I suspect because there are plenty of cases where you do need to be explicit about the data type, eg when using `useQueryData`, so habit/ consistency.