Learn / Upgrading to 0.41

foldkit-entity and foldkit-guard: the domain

  • A write's when that reads Expr.viewer or Expr.now (also through a path from the viewer or an exists) is refused where the write is declared. It used to fail only where a writer served it. A when reads the row and the input; who is asking is a guard rule's question.
  • evaluate refuses an order over text with no declared collation, which SQLite and Postgres would order differently. Declare one on the key you order by: Entity.annotateMembers({ title: Collation.of(Collation.binary) }), or Order.asc(field, { collation }).
  • An invariant belongs to the Entity, as its relations do, so every descriptor of it judges it. A test that piped different invariants onto one shared Entity gives each its own.
  • Security: every guard seam (GuardServer.writer, filter, memory and mutation, GuardDrizzle.visible, GuardSync.document and opens) throws where it is built when given a descriptor without guards of an Entity another descriptor of which carries them. Before, it served that descriptor unguarded. Pass the descriptor Guards.attach returned.
  • Entity.judgeInput(input, value, { operators?, over? }) takes an options object in place of the positional operator table.