zadam
Relation Constraints
When relating one note to another, you get a list of all possible notes that can be related.
If possible, add a statement for relation definitions constraints; for example:
#relation:isChildOf="promoted,inverse=hasChild,multi,constraints=person"
Attempting to fill out any isChildOf relation would only permit relating notes with the #person label.
I could also use this. My use-case is I have a simple issue tracking system in Trilium, and there's a relation between issues and their states ("open", "done", "waiting", "cancelled"). The issues also have "blockedBy" relations (which links issues to other issues they depend on), and "hotlist" relations (which should only link to #hotlist notes).
Yes, yes, and yes. Trilium is a powerful low-code database, the biggest lack of which imho is: Enumerations.
This would add enumerations in a very elegant way.
We can (and should) bikeshed how the constraint is specified, but any implementation is better that not having this.
Trilium has entered maintenance mode. Future enhancements will be addressed in TrilumNext: https://github.com/TriliumNext/Notes/issues/125
