Skip to content

fix: queryTreeListNoPage returns matched nodes instead of only roots (#9799) - #9855

Open
jeecgai wants to merge 1 commit into
jeecgboot:mainfrom
jeecgai:fix/issue-9799
Open

fix: queryTreeListNoPage returns matched nodes instead of only roots (#9799)#9855
jeecgai wants to merge 1 commit into
jeecgboot:mainfrom
jeecgai:fix/issue-9799

Conversation

@jeecgai

@jeecgai jeecgai commented Aug 25, 2026

Copy link
Copy Markdown

Summary

  • Tree list searches (hasQuery=true) always walked hits back to the global root, so condition queries returned a single root instead of the matched records.
  • queryTreeListNoPage now returns the matched forest (nodes whose parent is not also in the result), and the no-page API uses the result size instead of a hardcoded page of 10.

Fixes #9799

Test plan

  • Generate a tree entity from the online tree template and search with a name condition that matches non-root rows
  • Confirm the list shows those matched rows, not only the global root
  • Confirm more than 10 hits are all returned
  • Expanding the tree without a query still loads children by parent id as before

Condition queries no longer walk every hit back to the global root, and
the no-page list uses the result size instead of a hardcoded page of 10.

Fixes jeecgboot#9799
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

分页树形表格使用查询条件一直查询根节点问题,queryTreeListNoPage

1 participant