[wip] Attributes V2 #6421
Description
Describe feature
At the moment, this is a draft note meant to evolve into a spec/roadmap describing how to improve attributes in Trilium and address their current shortcomings and implementation complexities.
Key aspects include:
- clear separation between system-defined attributes used for configuration, and user-defined ones
- all attributes should be typed, with enriched options and validations (e.g. "is mandatory", "grater than", …), possibly with display options as well (render as a toggle, as a dial, …)
- no difference between typed attributes, promoted attributes, attributes definition: all user-defined attributes should render in-line as form controls, system-defined attributes may be managed in an power-user panel (like today) but should eventually find their way as GUI options
Additional Information
No response