Consume polyfill-surface, and declare what this package relies on
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 commit is contained in:
@@ -0,0 +1,9 @@
|
||||
<!-- generated — edit .project/concepts/*/_overview.md vocabulary blocks, then run lint --fix; do not edit this file -->
|
||||
|
||||
## Project vocabulary — canonical terms: use VERBATIM in any language, marked `like this`
|
||||
|
||||
```text
|
||||
«refine-binding»
|
||||
`resource` Refine's name for a data type an application declares and lists — bound here to one SHEX shape
|
||||
`binding` the translation this package performs between a Refine resource and NextGraph documents (never: adapter, bridge, glue)
|
||||
```
|
||||
Reference in New Issue
Block a user