Apply Mixins to a Type

A Mixin is a reusable schema bundle. It can supply properties and relations to several Types without changing their place in the inheritance tree.

The built-in Taskable Mixin is the clearest example: it supplies completion, due-date, and recurrence structure. A Task, Project, or another custom Type can be task-like without inheriting from one another.

Apply a Mixin

1. Open Object type settings → Mixins.
2. Choose an available Mixin.
3. Review the effective-schema preview.
4. Resolve any conflict before applying it.

You can also choose Mixins in the new-Type wizard before the Type is created.

Understand conflicts

Lar does not silently shadow two properties with the same name. If an own or inherited field collides with a Mixin field, the definition is rejected unless the schema explicitly defines the intended override. The creation and Type editors surface these conflicts before committing the change.

Remove a Mixin carefully

Removing a Mixin changes the effective schema of every Object of the Type. Check saved queries, views, templates, and automations that use its fields first. A field disappearing from the effective schema does not mean its historical meaning should be reassigned to a different property.

Mixin or inheritance?

Use inheritance for is a. Use a Mixin for has this reusable capability or structure. A Type can have one parent and multiple Mixins.

Next: Relations and backlinks.