If they do, this is a reasonable change for interop reasons, even if it doesn't make much logical sense. The goal is just to invoke PouchDB behavior that is optimized for remote adapters, i.e. adapters where it's expensive to cross some kind of boundary (http, web sockets, worker, etc.).
One good way to test interop issues with https://github.com/pouchdb/pouchdb/issues/6106 is to just change the
type()to'http'and see if the tests still pass.If they do, this is a reasonable change for interop reasons, even if it doesn't make much logical sense. The goal is just to invoke PouchDB behavior that is optimized for remote adapters, i.e. adapters where it's expensive to cross some kind of boundary (http, web sockets, worker, etc.).