[#73350] Use single selection tree view with search for page selection#23493
Conversation
|
Caution The provided work package version does not match the core version Details:
Please make sure that:
|
04368ef to
9d17a54
Compare
|
Probably a feedback for the tree view, rather than for this PR: When the search text does not exactly appear in the resulting tree view, then nothing is highlighted. I guess this is acceptable for now, but should we track it as a bug?
CC @HDinger |
Yes, I noticed that on my branch as well. I think a separate bug makes sense 👍 |
03f82b1 to
67b53bb
Compare
f575027 to
4ec38b7
Compare
|
🔴 I guess this is a bug in the selectable tree view, but it affects us a lot: Screencast.from.2026-06-03.10-48-21.webmWhat do you see? When there are multiple pages with the same name (but different values) you can only select the first one. This is bad, because our internal wikis have a lot of different root pages that commonly have the same name. While this is also a reminder that we should add additional information to the nodes, it's surprising to me that the selection doesn't work in this case. |
Oh, you are right. I also noticed it, and I wanted to talk to @HDinger about it. The main issue is, that the tree view component identifies its items by the path, not a hidden identifier below. The question now is, should we try to fix that or basically wait until we have the hierarchy, which fixes then at least the page that have different ancestors. BUT: In a wiki it is NOT disallowed, to have pages with the same title under the same parent. This is true for both, our internal wiki AND XWiki. So, we won't be able to catch every case with unique paths. Will take that into discussion, but I think, it shouldn't be a blocker to this PR, which only introduces the component in a not final way. UPDATE: Bug ticket was created: https://community.openproject.org/wp/SDS-704 |
4ec38b7 to
87b0d62
Compare
- https://community.openproject.org/work_packages/73350 - render search results in a tree view
- use new filterable tree view component with server side filtering - remove unused classes and methods - add document icon for page results - add comment to disabled authorization - moved filterable tree to the form class
87b0d62 to
e9157b8
Compare



Ticket
#73350
What are you trying to accomplish?
What approach did you choose and why?