You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Feature Request: Support Type Inheritance / Subtypes (via belongs_to or similar)
#1289
Currently, types in Tolaria exist in a flat hierarchy. As a vault grows, broad categories (like Event) quickly become cluttered. If a user creates a more specific type (like Meeting), there is no native way to link it to the parent Event type, forcing users to choose between broad categorization and granular organization.
Proposed Solution
Introduce support for subtypes (type inheritance). For example, a user should be able to define Meeting as a subtype of Event.
Expected Behavior:
Inheritance: A note of type Meeting inherits the properties of Event and is recognized by the system as both a Meeting and an Event.
Views & Queries: Under the Types view, notes created as a Meeting should appear under both Meeting and Event (or within a nested hierarchy).
Dynamic Vault Scaling: Users can start with simple, broad types (Event) and organically introduce granular subtypes (Meeting, Workshop, Conference) later without breaking their existing structure.
Suggested Implementation
Repurpose the belongs_to field within the Type Definition file to establish parent-child relationships between types:
Current behavior: Setting belongs_to in a type definition sets a default file link for every instance created of that type. In practice, there are very few use cases where every single instance of a type (e.g., every Event) belongs to the exact same file.
Proposed behavior: Defining belongs_to: Event inside the Meeting type definition designates Meeting as a subtype of Event. (Alternatively, if backward compatibility for default values is needed, a new property like subtype_of or extends could be introduced).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem Statement
Currently, types in Tolaria exist in a flat hierarchy. As a vault grows, broad categories (like
Event) quickly become cluttered. If a user creates a more specific type (likeMeeting), there is no native way to link it to the parentEventtype, forcing users to choose between broad categorization and granular organization.Proposed Solution
Introduce support for subtypes (type inheritance). For example, a user should be able to define
Meetingas a subtype ofEvent.Expected Behavior:
Meetinginherits the properties ofEventand is recognized by the system as both aMeetingand anEvent.Meetingshould appear under bothMeetingandEvent(or within a nested hierarchy).Event) and organically introduce granular subtypes (Meeting,Workshop,Conference) later without breaking their existing structure.Suggested Implementation
Repurpose the
belongs_tofield within the Type Definition file to establish parent-child relationships between types:belongs_toin a type definition sets a default file link for every instance created of that type. In practice, there are very few use cases where every single instance of a type (e.g., every Event) belongs to the exact same file.belongs_to: Eventinside the Meeting type definition designates Meeting as a subtype of Event. (Alternatively, if backward compatibility for default values is needed, a new property like subtype_of or extends could be introduced).All reactions