There are valid use cases when we want to allow users to be able to clear all data in the browser without sending any requests to the server.
By default, we try to sync all local changes first, then send a request to invalidate the session. If either fails, account.signOut() rejects with a request or authorization header.
But
if user does not care about local changes and is currently offline and want to remove all their local data, we should allow to do that
The account might have been removed from the server and there is currently no built-in way to remove the data in the browser. This happens quite often for local development and is rather annoying
ignoreLocalChanges does not communicate that we don’t send a request at all, but I think it communicates pretty well the implication to the user
There are valid use cases when we want to allow users to be able to clear all data in the browser without sending any requests to the server.
By default, we try to sync all local changes first, then send a request to invalidate the session. If either fails,
account.signOut()rejects with a request or authorization header.But
ignoreLocalChangesdoes not communicate that we don’t send a request at all, but I think it communicates pretty well the implication to the user