type.unknown_setting: Setting is not one Jadpo knows

Setting is not one Jadpo knows.

Area 2, Values and types; not declinable; the next step is usually the agent's.

A type's block holds only the constraints in the table above:

example

type ProductName = Text {    min_length: 1    maxlength: 120}

jadpo checkcheck failed: 1 error, 1 file

error maxlength isn't a setting Jadpo knows

--> main.jadpo:3:5

  |3 |     maxlength: 120  |     ^^^^^^^^^ unknown setting

reason: A type's block holds the constraints min, max, min_length, max_length, pattern, format, scale, version, currency, rounding, from, to, dimensions and distance. Did you mean max_length?
next: Use max_length instead of maxlength (agent)
rule: type.unknown_setting
help: https://jadpo.dev/docs/errors/type.unknown_setting

personal: is a setting of a field where Jadpo keeps or sends its value: an entity's, an event's or an email's, or an object's, an input's or an output's that a package declares (Marking personal fields). An app's own type holds what a marked field gave it, and the value is followed back to that field:

example

/// A card shown to someone.type Card = Output {    name: Text {        personal: PersonalData.identifying    }}

jadpo checkcheck failed: 1 error, 1 file

error personal isn't a setting of Card's fields

--> main.jadpo:4:9

  |4 |         personal: PersonalData.identifying  |         ^^^^^^^^ unknown setting

reason: personal: marks a field of an entity, an event or an email, or of an object, input or output a package declares, where Jadpo keeps or sends its value. Card is none of these: a value in it is followed back to the marked field it came from, so it needs no mark of its own.
next: Remove personal, and mark the field its value is read from (agent)
rule: type.unknown_setting
help: https://jadpo.dev/docs/errors/type.unknown_setting

Related