-
-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for alias notes #128
Comments
I like this idea a lot. The main concern I have is if two notes have the same alias, where a file name conflicts with the alias name in the tree view. Right now, in this case, I think the file name should win out, and possible the file name could include a link to the alias notes, possibly as a metadata, or transcluded in the body of the document. Perhaps by default, if an alias is created, a note should be created with the file name corresponding to the tree node with the aliased note transcluded in it. There are a lot of ways to approach this. Also, what would be the benefit of this approach as opposed to create a note that transcludes or links to the existing note? I'm not even sure if there would be benefits in the graph view.(#1916 (comment)). #1916 |
@sahil48 On the topic of what is the benefit of just regular link, there is a huge benefit between just the link since alias would allow you to open the note right away instead of having another navigation hop to get from a stubby alias note to the actual note which contains the content. |
I think this is a good idea to make the alias visible in the filesystem. |
This issue is featured in this week's round of CROP voting. |
Will this require extra functionality in the export pods to convert to standard Markdown? |
Adding this article https://www.goedel.io/p/the-importance-of-aliases about the topic. |
just want to voice my support for this! i'm a couple days into porting my notes to dendron from a more pure network graph system and already hitting the need for these, would be a huge feature for my use. 🙏🏻❤️ |
This would be ideal for publishing, since one could create a vault with a hierarchy of aliases to files one wants to publish without having to move those files from their original hierarchy. Using the file system seems to make sense for build/tooling reasons because the file system already has that functionality, but if having the alias as front matter is what dendron needs to knows about the relationship, so be it. Long as I can publish vaults with aliases in their hierarchies, that would add a lot of flexibility to potential publishing workflows. If there's a way to do this already, please inform... |
Context
There are some cases when you want the same note to have multiple paths. See this and this
Proposal
Introduce note aliases, a way to map the same note to multiple paths.
Example
Say you have the following note
python.lib.pandas
python.lib.pandas
The text was updated successfully, but these errors were encountered: