Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query results hierarchy is not shared and is instead repeated for each child of a shared parent block in newer versions #6973

Open
mfrvnken opened this issue Oct 13, 2022 · 1 comment

Comments

@mfrvnken
Copy link

What happened?

Queries in more recent version behave differently in the way they display order and hierarchy specifically with task queries (I have no tried it with other queries).

I have Logseq version 0.7.5 installed on one machine and version 0.8.8 installed on another machine. I have a simple query in my Journal template that is as follows.

{{query (and (task todo doing now later done cancelled) <% today %> )}}

Reproduce the Bug

Install Logseq versions 0.7.5 and 0.8.8 and add the following page to both of them.

pages/Test Page.md

# [[To Do]]
	- {{query (and (task todo doing now later done cancelled) [[Test Page]] )}}
# [[Thoughts]]
	- TODO Carryover or cancel yesterday's tasks.
	- ## Carryover from [[Oct 13th, 2022]]
		-
	- TODO do the the thing
		- TODO sub thing
		- TODO another subthing
	- TODO another thing
	- ## Heading 2
		- TODO heading 2 todo

view query results in each version of Logseq

Expected Behavior

Query results with shared parent blocks should be groups together under one instance of that shared parent block.
See expected screenshot.

Screenshots

Expected - 0.7.5
Logseq_oe4DbKObpZ

Actual - 0.8.8
Logseq_fDtu5MhHE4

Desktop Platform Information

Windows 10 Pro 10.0.19044 Build 19044, App, 0.8.8
Windows 10 Pro 10.0.19044 Build 19044, App, 0.7.5

Mobile Platform Information

Not tested

Additional Context

No response

@cnrpman cnrpman added the query label Oct 14, 2022
@ndc33
Copy link

ndc33 commented Mar 20, 2023

Hi, just to say I think this is big issue; and its effects get much worse when the example gets bigger (it makes queries unusable for complex e.g. workplace multi-stage tasks). Would greatly appreciate this having a higher priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🗄 Backlog
Development

No branches or pull requests

4 participants