You're directly calling close() in the render path

This is a really confusing, unclear line. You should separate it out into two to make it more clear

You can't just be setting local variables like that willy-nilly from a callback. If you have some state you want to track inside a Hook, you must use useRef or useState

It's really weird to be setting this callback to undefined from within the callback. Even if you were doing it properly with a ref or state, it's still a confusing pattern. You should have the callback defined as a const using React.useCallback (standard), and instead have some boolean React.useRef that tracks whether a callback should be passed to useToggleUnreadStatus

You're right. This was an oversight. When moving the current.close into a callback I forgot to remove the swipeableClose variable assignment.

Agreed. 200%, mutating state like this is awful, I should have caught it.

Agreed. This was an oversight.

I don't think I need to track if the callBack was passed in or not.

Now that you're no longer setting the callback to undefined, there's no need to make useToggleUnreadStatus support an undefined / null callback

We don't need this change here, let's avoid adding to the Git history for this file unless we really need to

This accidentally got pulled back in