Should
micebe clickable there? If it’s there because it’s easier to implement aliases when that page exists, perhaps have an indicator that it is an alias page and/or prevent people from adding content to those pages.
I think it depends on how you use aliases, if you just need several different aliases which link to the source page, it shouldn’t be clickable. But, if the aliases have their own contents, it needs to be clickable. For example, I have a page written in English and a translated one in Chinese, I don’t want to mix the Chinese content in the source page. Another use case might be when you need to include or reference to other people’ pages.
When I added text to a block on page “mice”, it seemed to create a file “mice.md”, but the content there is not shown on the “mouse” page.
The content (blocks) will be listed in the linked references section, we can’t automatically update the mouse page when you add a block on page mice because those pages are equal in their names but not always in their contents.
I agree with cannibalox that having aliases suggested in page autocomplete would be a great next step after they are working well.
Totall agree! @cannibalox any ideas on the UX? Listing the aliases under the top matched page?
As always, I am a user and not a programmer, so let me know if my suggestions are ignoring technical limits.
I don’t think there’re technical limits, it really depends on how you use aliases, we can only warn when users want to insert any blocks to the alias page using logseq, but if people use other editors to edit the markdown/org file, it’s still a problem. I think we can add a configuration option alias/disable-link-in-source-page? so that the aliases will not be clickable in the source page, what do you think?