Engine

2.1. Defining events🔗

Events go in the events section of a definition file, with the entity's key field; how fields and their types are written is on Files and requests. A field ending in ? is optional.

The engine gives every event engine field names: entity, type, key, at, revision, expected_revision and position. A file may not use one of them for a field of its own. Here the folio's FolioOpened has a field named at:

      FolioOpened:  { reservation_id: text, at: text }
folioWithFieldNamedAtText · checked against the spec ·

A field named at is rejected on deploy.

A field named at is rejected on deploy.

The general rules of a definition: