Replies: 1 comment 1 reply
-
Yes, this is logic built in logseq copilot. This thing has 2 common use cases:
In this case 1, I am considering solutions for this:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi there, I would like to discuss use cases like mine: the internal doc platform uses parts after # in the url to route to different docs.
For logseq copilot (which is awesome), it seems the parts after # is ignored when search logseq graph. For example, if I open some doc at sub.xxx.com/doc/#id=yyy, all url in the logseq graph which matches sub.xxx.com/doc/ will display in the plugin popup. They are actually different docs, so the search results in this use cases is not that useful.
Whether this due the design of logseq copilot plugin or logseq search api itself?
Beta Was this translation helpful? Give feedback.
All reactions