Dockery/Trilium
1
0
Fork 0
mirror of https://github.com/zadam/trilium.git synced 2025-11-09 06:45:49 +01:00
Code Issues Packages Projects Releases Activity

feat(docs): document the hidden tree

Browse Source
This commit is contained in:
Elian Doran
2025-04-07 13:29:22 +03:00
parent 5130089b34
commit 6cc10a47d1
15 changed files with 797 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
docs/User Guide/User Guide/Advanced Usage/Attributes/Attribute Inheritance.md
View File

@@ -9,19 +9,30 @@ To make an attribute inheritable, simply use the visual editor for <a class="re
As an example, the `archived` label can be set to be inheritable, allowing you to hide a whole subtree of notes from searches and other dialogs by applying this label at the top level.
Standard inheritance forces all the notes that are children (and sub-children) of a note to have that particular label or relation. If there is a need to have some notes not inherit one of the labels, then _copying inheritance_ or _template inheritance_ needs to be used instead.
## Copying Inheritance
Copying inheritance differs from standard inheritance by using a `child:` prefix in the attribute name. This prefix causes new child notes to automatically receive specific attributes from the parent note. These attributes are independent of the parent and will persist even if the note is moved elsewhere.
### How to Use
If a parent note has the label `#child:exampleAttribute`, all newly created child notes (one level deep) will inherit the `#exampleAttribute` label. This can be useful for setting default properties for notes in a specific section.
* **Syntax:** `#child:attributeName`
* **Chained Inheritance:** You can chain this inheritance, such as `#child:child:attributeName`, where each child down the hierarchy receives the appropriate attribute.
Similarly, for relations use `~child:myRelation`.
### Example
Due to the way it's designed, copying inheritance cannot be used to cascade infinitely within a hierarchy. For that use case, consider using either standard inheritance or templates.
If a parent note has the label `#child:exampleAttribute`, all newly created child notes will inherit the `#exampleAttribute` label. This can be useful for setting default properties for notes in a specific section.
### Chained inheritance
It is possible to define labels across multiple levels of depth. For example, `#child:child:child:foo` applied to a root note would create:
* `#child:child:foo` on the first-level children.
* `#child:foo` on the second-level children.
* `#foo` on the third-level children.
Similarly, use `~child:child:child:foo` if dealing with relations.
Do note that same as simple copying inheritance, the changes will not apply retroactively to existing notes in the hierarchy, it will only apply to the newly created notes.
## Template Inheritance
Attributes can also be inherited from [templates](../Templates.md). When a new note is created using a template, it inherits the attributes defined in that template. This is particularly useful for maintaining consistency across notes that follow a similar structure or function.
Attributes can also be inherited from <a class="reference-link" href="../Templates.md">Templates</a>. When a new note is created using a template, it inherits the attributes defined in that template. This is particularly useful for maintaining consistency across notes that follow a similar structure or function.