File operations for an Aquabase project. Buckets materialize automatically
on the first authorized upload — there is no explicit createBucket.
Whether a path is publicly readable is determined entirely by your storage
rules.
Hosted sign-in handed to the browser: url is what the user opens,
secret is what redeems the resulting session. Only the digest of the
secret travels, so nothing in the URL can claim the session.
The matching documents in plan order, plus the provenance of the answer.
docs is unmodifiable: a watcher keeps the same snapshot it emitted, and
a consumer mutating it would corrupt the comparison against the next one.
A background write the server never accepted — unreachable, or rejected by
the rules. The local value stands, except on a denial, which is reverted
before this is reported.
Where a result came from. cache never means "the server said nothing", and
local is not a cache at all: a local-only collection has no authority
above the device, so its answer is complete by definition.
Typed reads over a decoded document. The representation is the decoded
map — the wrapper is erased at compile time, so nothing is copied and no
object is allocated to obtain one.
Native Google sign-in could not run: the project has no Google provider
enabled, the platform has no native sheet, or Google rejected the attempt.
The message says which. Callers wanting a plan B can still drive the
hosted flow themselves with startOAuthPairing / awaitOAuthPairing.
Thrown when a write would repeat a value a unique group already holds.
holder is the key of the document that has it, fields the group in the
order the manifest declares — the order its values were hashed in.
