Opens the brief that holds this binding to `@activitypods/refine-providers`,
with which it must be interchangeable, and settles its six questions. The
decisive finding of the comparison: the reference asks its server for almost
none of what a Refine resource needs — filters, sorting, pagination and
totals are computed in memory there too — so most of the gap is this
package's own work rather than the polyfill's.
What the engagement is now asked for, in order: a shape-typed write and
removal that can be awaited outside React, a call that closes a session, a
display name, and a write-ownership predicate that would let an interface
hide a control instead of letting it fail.
Two corrections worth their own mention, both found by review rather than
by reading further:
- a non-guarantee about how strongly the upstream authenticates was being
allowed to dictate the SHAPE of this binding, which had `login` and
`logout` published as having no surface. Opening a wallet is the act the
target will have, so the auth provider is wired to it and the missing
closing call is a request, not an absence of analogue;
- what is internal to the emulation must not be known in this repository at
all. Restating it here would duplicate a claim this package cannot verify
and would teach an application a distinction that disappears at migration.
Sylvain Duchesne
259d7fe58d