Interface: ObjectSchemaDefinition<K, L>¶
A schema definition for an object value (a value with key-value pairs).
Attribution text, images, and/or links that should be rendered along with this value.
A hint for how Coda should interpret and render this object value.
For example, an object can represent a person (user) in a Coda doc, with properties for the
email address of the person and their name. Using
ValueHintType.Person tells Coda to
render such a value as an @-reference to that person, rather than a basic object chip.
A explanation of this object schema property shown to the user in the UI.
If your pack has an object schema with many properties, it may be useful to explain the purpose or contents of any property that is not self-evident.
The name of a property within properties that be used to label this object in the UI. Object values can contain many properties and the Coda UI will display them as a "chip" with only the value of the "displayProperty" property used as the chip's display label. The other properties can be seen when hovering over the chip.
A list of property names from within properties for the "featured" properties of this object, used in sync tables. When a sync table is first added to a document, columns are created for each of the featured properties. The user can easily add additional columns for any other properties, as desired. All featured properties need to be top-level. If you can't or don't want to change the received data format, consider changing the received object after fetching and before returning and assigning it to the schema.
This distinction exists for cases where a sync table may include dozens of properties, which would create a very wide table that is difficult to use. Featuring properties allows a sync table to be created with the most useful columns created by default, and the user can add additional columns as they find them useful.
Non-featured properties can always be referenced in formulas regardless of whether column projections have been created for them.
The name of a property within properties that represents a unique id for this object. Sync table schemas must specify an id property, which uniquely identify each synced row.
An identity for this schema, if this schema is important enough to be named and referenced. See IdentityDefinition.
Specifies that object instances with this schema can contain additional properties not defined in the schema, and that the packs infrastructure should retain these unknown properties rather than stripping them.
Properties not declared in the schema will not work properly in Coda: they cannot be used natively in the formula language and will not have correct types in Coda. But, in certain scenarios they can be useful.
Definintion of the key-value pairs in this object.
Identifies this schema as an object schema.