foldkit-entity 0.18.0 → 0.19.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +9 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1108,6 +1108,15 @@ optional relation set to nothing), and each interpreter carries it its own way,
|
|
|
1108
1108
|
a ref key in a store, a foreign key in a table. A `many` relation or a nested
|
|
1109
1109
|
key is refused where the write is declared.
|
|
1110
1110
|
|
|
1111
|
+
An application sends a write as a `foldkit-remote` mutation,
|
|
1112
|
+
`Mutation.write(name, write)`, which names it and types what it may be refused
|
|
1113
|
+
with. When the input is the row's `id` and fields named for themselves,
|
|
1114
|
+
`Mutation.update('EditPost', Blog.Post, { set: { title: Schema.String } })`
|
|
1115
|
+
(and `Mutation.insert`, `Mutation.delete`) is the same mutation in one call:
|
|
1116
|
+
the input, the write and its name. The input and the write stay values of
|
|
1117
|
+
their own here, since a form is built from the input alone, and every writer
|
|
1118
|
+
and `Laws.check` read the write.
|
|
1119
|
+
|
|
1111
1120
|
### Values no client chooses: `Entity.sets`
|
|
1112
1121
|
|
|
1113
1122
|
Some values no client should choose: who wrote a row, and when. The Entity
|
package/package.json
CHANGED