Referential stability of the mutation object
The useMutation hook consistently returns properties with stable references, however, the hook itself produces a new object with each use. As a result, directly including the entire mutation object in dependency arrays can be problematic. Is this design a deliberate prompt to encourage developers to only add the specific properties they require to their dependency arrays (thus adhering to best practices)?
