logseq / db-test

Used for Database version test
8 stars 1 forks source link

Page names with page references #111

Open nckre opened 2 months ago

nckre commented 2 months ago

Search first

What Happened?

When creating a page that consists of other pages inline (e.g. [[[[Hello]][[World]]]]) the page reference looks empty in the UI.

CleanShot 2024-09-19 at 13 51 39

However, can create a working page like [[[[Foo]] [[Bar]]]] by renaming an existing page and it will be displayed correctly inline:

CleanShot 2024-09-19 at 13 56 00

When editing the above (e.g. removing space so that [[[[Foo]] [[Bar]]]]) the inline page ref becomes empty. When re-adding the space the inline ref now displays the node references rather than the page titles.

CleanShot 2024-09-19 at 13 58 01

Reproduce the Bug

  1. Write [[[[Hello]][[World]]]] into a node

Expected Behavior

No response

Screenshots

No response

Browser, Desktop or Mobile Platform Information

No response

Additional Context

No response

Are you willing to submit a PR? If you know how to fix the bug.

logseq-cldwalker commented 1 month ago

Hi. Pages with refs in their name have a rich history of being buggy as they introduce a lot of edge cases. This bugginess isn't something specific to the db version and so it's less interesting unless you're proposing the behavior change for the db version

nckre commented 1 month ago

@logseq-cldwalker hey, my perspective for alpha test:

I have no insight into what might cause proper issues with DB concistency vs. what's just a small visual thing So no worries about ignoring any of the issues I'm raising - some seem very niche to me too :)

Regarding "proposing behaviour change" for nested page refs: I do believe this could be useful. But if a feature has a "a rich history of being buggy" and there are more important things to build -> maybe you should forbid nested references for now, same as you did with /