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.
The Change policy asks for a tag carrying the package name, and one now
exists for this version, so the pin moves off the authoring branch onto
`polyfill/v1.0.0-dev.15`.
That version answers standing requests of its own: a read of a document
named in `graphs` now reaches it before the query opens, a shape query
hands back the shape's objects rather than property bags, and the leaf
gained an "Asked for, not decided" list where an application's request
leaves a trace instead of living in a message.
Pulls @ng-eventually/polyfill's engagement, version-pinned, and declares
back what this package actually consumes — the contract pair that lets the
two repositories coordinate without either reading the other's source.
The declaration is the channel: its Frictions and Needs are standing
requests the provider drains. The one that decides this package's shape:
modifying and removing a record have no published path that is both
shape-typed and awaitable, so Refine's update and deleteOne have nowhere
to land. Reading, creating and both live channels do have one.
The engagement describes 1.0.0-dev.14 and no tag carries it, so the pin is
the branch it is authored on and `against:` is the commit it resolved to.
This repository is a sibling of @ng-org/refine-providers, not a successor:
that one binds a Refine application to the NextGraph SDK as it is today,
this one will bind it to @ng-eventually/polyfill, which stands in for the
SDK that has not shipped yet. Both have a legitimate existence and an
application may move from one to the other.
The scope says which of the two a dependency line is asking for.
Sylvain Duchesne