You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like this is a new bug after the new addition to the namespace feature at logseq/logseq@af55aa9
When writing a block that includes links to nodes in hierarchies with the same name, the links get switched to point to the same node.
Reproduce the Bug
Make a node [[Math Work/Ch. 1]] and a node [[Physics Work/Ch. 1]]
Write a block that links to both of the above nodes. The links should be inserted using the autocomplete menu to ensure that the correct blocks are linked to.
Hover over the links.
Expected Behavior
I expect the links to point to the selected nodes in Math and Physics hierarchies as I specifically selected. Instead they point to the same node, evidently the node that was last written dictates the link heritage.
Screenshots
output.mp4
Browser, Desktop or Mobile Platform Information
OS: NixOS Unstable
Browser: Version 130.0.6723.69 (Official Build, ungoogled-chromium) (64-bit)
Logseq: 0.10.10 b250e26 at test.logseq.com
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
I'm willing to submit a PR (Thank you!)
The text was updated successfully, but these errors were encountered:
Search first
What Happened?
Looks like this is a new bug after the new addition to the namespace feature at logseq/logseq@af55aa9
When writing a block that includes links to nodes in hierarchies with the same name, the links get switched to point to the same node.
Reproduce the Bug
Expected Behavior
I expect the links to point to the selected nodes in Math and Physics hierarchies as I specifically selected. Instead they point to the same node, evidently the node that was last written dictates the link heritage.
Screenshots
output.mp4
Browser, Desktop or Mobile Platform Information
OS: NixOS Unstable
Browser: Version 130.0.6723.69 (Official Build, ungoogled-chromium) (64-bit)
Logseq: 0.10.10 b250e26 at test.logseq.com
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
The text was updated successfully, but these errors were encountered: