Usage of useUser with useFirestoreDocData not very compatible within custom hooks

まず、useUser、useFirestore、useFirestoreDocData のエントリーポイントを追跡し、issue に示されているカスタムフックを使って null-user のパスを再現します。報告されている ReactFire v4 の動作を、issue 249 で参照されている ReactFire v3 の動作と比較します。この issue では、ファイル、テスト、具体的な完了基準のいずれも指定されていません。

Version info

React: 18 experimental

Firebase: 9

ReactFire: 4

Other (e.g. Node, browser, operating system) (if applicable):

Test case

Steps to reproduce

const useMyHook= () => {
    
    const firestore = useFirestore();
    const {data: user} = useUser();   
    const ref = user && doc(firestore, "users", user.uid);
    const {data: userData} = useFirestoreDocData(ref);

    return userData;
}

Behavior

Since useUser is returning the type User | null , we need to check, if the user is available. But in the case when the user is null, useFirestoreDocData cannot be called, since the ref would not exist. In react we are not allowed to write:
const {data: userData} = ref && useFirestoreDocData(ref)

One way to get around this issue is by passing in the user as a prop, but it does not seem to be convenient, if one wants to use this hook within another hook. We would just push the issue upwards until we reach a component that is again wrapped by a component that knows if the user exists:

• component that checks if user exists (like deprecated AuthCheck)
• component that is rendered when user exists
• hook that is called within that component

Another alternative for typescript is writing user! with exclamation mark, but this does not feel proper.

I hope the case is clear and you might know a better way to deal with it.
I think with react-fire v3 (fb v8) I wasn't experiencing this issue. Since it was probably solved with this issue: https://github.com/FirebaseExtended/reactfire/issues/249