Hide aliases circles in Graph View

aces · January 27, 2023, 11:59pm

+1 Please make this adjustment, as aliases are not even real pages on the Disk…

Here are some more references about this - it’s a feautre much more needed than it may seem just based on this one thread…

github.com/logseq/logseq

Page property 'exclude-from-graph-view' doesn't work in 'Page graph'

opened 04:27AM - 23 Sep 22 UTC

skydtrtzmr

:type/enhancement graph props estimate: medium

### What happened? Pages with property `exclude-from-graph-view:: true` are hid…den in **Graph view**, but not hidden in **Page graph**. ![image](https://user-images.githubusercontent.com/45526359/191888106-c5df8dfe-8420-41ca-ac10-b5a6c3567019.png) ![image](https://user-images.githubusercontent.com/45526359/191887680-33b6ba9e-aad7-4fbe-ae49-00b68600be1c.png) （and **aliases** are still duplicating in the graph view🙁) `exclude-from-graph-view:: true` does make the Graph view much clearer. It would be nice if this property could work in **Page graph** too. Can we have an option to hide those with 'exclude-from-graph-view:: true' in **Page graph** too? ### Reproduce the Bug 1. Create a page [[A]] with property `exclude-from-graph-view:: false`, and a page [[B]] linked to [[A]] with property `exclude-from-graph-view:: true`. 2. See node of page [[A]] in **Graph view**. [[B]] is not shown. 3. See the graph of page [[A]] in the sidebar. Node [[B]] is shown in **Page graph**, connected to node [[A]]. ### Expected Behavior Maybe we can have an option in **Page graph** to hide pages with property 'exclude-from-graph-view:: true' . And it would be better to make it possible to focus on a certain node in **Graph view** (as what we see in **Page view**). ### Screenshots _No response_ ### Desktop Platform Information Win10, v0.8.7 ### Mobile Platform Information _No response_ ### Additional Context BTW, I couldn't find a way in **Graph view** to focus on a certain node and see other nodes linked to it, just like in **Page graph**. Sometimes I just want to focus to different nodes quickly in Graph view. Usually, when I search *'pagename'* in **Graph view**, I actually want to filter only the nodes that connect with [[pagename]] , rather than filter the nodes with the *'pagename'* in their names. I would be grateful if there is any suggestion on what I am looking for.❤

github.com/logseq/logseq

[Bug] Page alias is shown on the graph

opened 07:09AM - 03 Sep 21 UTC

closed 10:14PM - 12 Jan 23 UTC

the-jb

**Describe the bug** With not creating any page on alias, the alias page should… not be on the graph. But it is shown on graph **To Reproduce** Steps to reproduce the behavior: 1. create page [[my page]] with adding properties `alias:: ali` 2. ref [[ali]] from other pages 3. Look at the graph **Expected behavior** pages are referencing 'ali', and 'ali' reference 'my page' **Desktop (please complete the following information):** - OS: Windows - Browser: chrome - Version: 0.3.7

github.com/logseq/logseq

Aliases are duplicating in the graph view and the searching result

opened 05:15AM - 24 Mar 22 UTC

Konfido

:type/enhancement graph search ux page-ref props:alias

### What happened? I found the alias feature works in an unusual way, and aft…er checking this issue https://github.com/logseq/logseq/issues/4342#issuecomment-1048049248 and the related discussion, I figured it out and think it's really nice. > this is actually a feature, not a bug : > * if [[aliaspage]] is empty, all links are redirected to [[sourcepage]] > * if [[aliaspage]] has a different content from [[sourcepage]],links are displayed as linked refs in the sourcepage > > you can read more about the implementation and arguments in this topic: [discuss.logseq.com/t/improve-implementation-of-aliases/81/8](https://discuss.logseq.com/t/improve-implementation-of-aliases/81/8) BUT, here is what I cannot figure out: - If there no content/page for some alias which means they're **identical** to the "source" and not in a link-and-backlink connection, why link all the alias to each other in the graph? And it makes no sense to link all the backlinks to them separately. This causes tons of duplications in the graph view and create a huge obstacle to figure out the real relationship among them. - Same for the searching result. Instead, you could only show the source node, and list all its alias beneath it. It will make the result way much clearer and may also alleviate the potential performance issues. I list some of my rough thoughts in the following. Please consider improving current graph view experience. Thank you. ### Reproduce the Bug Just preview a page with a couple of alias. ### Expected Behavior _No response_ ### Screenshots - For a set of alias nodes: - `test1` is the source file - `test2` and `test3` is alias to `test1` and has no content. - `testing` is alias to `test1` but has different content. - `foo1` is linked to source file `test1` - `foo2` is linked to alias `test2` - `foo3` is linked to alias `testing` - A possible alternative for the graph view: <img width="1363" alt="solution" src="https://user-images.githubusercontent.com/25447610/159845456-aabfdeef-8eea-4c9d-9bc6-5df27c2accd7.png"> - Possible alternative for the search result: <img width="909" alt="Xnip2022-03-24_12-57-44" src="https://user-images.githubusercontent.com/25447610/159845488-c7ad2ec6-5f65-44dc-90ef-4f36a887bc34.png"> ### Desktop Platform Information - MacOS 10.15.7 - logseq 0.6.4 ### Mobile Platform Information _No response_ ### Additional Context _No response_

Looks like there was a fix, but not complete: Fix: "Page aliases are unaffected by the page property exclude-from-graph-view" by 8N9KT · Pull Request #6241 · logseq/logseq · GitHub