error schema-lock

What it means#

oxl.schema.lock sits next to oxl.toml and records the tags of the wire schema. The compiler reports this error when the file cannot be parsed (the message names the line), or when oxl build --locked finds that the lock would have to change: with --locked (for CI) the schema must already be committed.

Example#

// `oxl build --locked` after the field `note` was added and the lock was not updated
pub(api) data Order {
  id: i64
  note: str?             // <- schema-lock
}

A malformed lock (kind = "banana" in a [types."shop.Order"] table) is reported with the line of the problem.

How to fix#

Run oxl build without --locked and commit the updated lock file, or repair the hand edit. Deleting the lock lets the compiler assign fresh tags: this loses the compatibility guarantee, which is why oxl publish compares against the last published lock instead (прил. C.3).

See also#

• schema-break