Update: add a enabled argument

[ticketapp]

Also, it would be very cool to have a enabled field for useDocument and useCollection as with react-query.
Currently what I do is

const [studiesData] = useCollection(
    studiesCollection,
    where('userUid', '==', user?.id || 'DOES_NOT_EXIST')
  );

But the query is still done with "DOES_NOT_EXIST"

Thanks again for your work

[0x80]

Seems like a nice idea. However, I haven't needed it myself in 8 years ;)

The abstractions for react are currently a thin wrapper around the forked react-firebase-hooks. When I rewrite it I will consider putting it in.

In your particular example I wouldn't expect the code to land on that component if user / user id is not available. That is typically how I solve things. You shouldn't have to do a query on a user id if you do not know the user yet.

I structure my authenticated code such that the user is always guaranteed to be there and Typescript is aware of it.

[ticketapp]

Thanks for your answer.

I use Clerk hook to get the user and generally the user id is instantly returned but it happens that it's not. Other thing is that it always returns string | undefined even if it's in an authenticated part of the app and it'd cleaner to have enabled(user?.id) instead of "does-not-exist"
But that's not a big deal

[0x80]

You can probably work around that, because you don't have stick with whatever type is returned. If you are sure the user is in the authenticated part of your app, you can make a hook that wraps things and performs an assertion on the response of the original hook, to make sure it is defined (or throw an error) Then the rest of your code can work with the assumption that the data is available.