Replies: 0 comments 1 reply
-
I guess a solution to my real problem would be to have a way to declare the sorting behavior of templates :
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Basically, my goal was to clean my tree a little bit, and group templates into template types. (please remember this, as this is the real problem, not the one I created myself below).
Solution 1: group the templates in an intermediate branch note with the given template type as title
⇒ Problem : Doing so, I lost alphabetical sorting when assigning a new note to its template 😵💫
Solution 2: Creating an inheritable label in note
Templates
Problem : all the implementations of this template will inherit the label too, but
templateType
is an information that should only belong to a template, not its implementations.So, two questions:
(truth is, coming from Java, I even split templates into two types: Classes, that really build something new, like a Person, a City, etc., and Interfaces, a toolbox of recurrent building blocks that can be reused here and there in different templates, like 'advanced tags', generic child/parent relationships, contact information, etc.)
Beta Was this translation helpful? Give feedback.
All reactions