Problem
Cloud search results can show multiple files with similar or hash-like names. The list currently makes it hard to understand where a search result is located without opening or interacting with it further.
Example scenario:
- A user searches inside Cloud.
- Several matching files have similar names.
- The user wants to know which folder each result belongs to before opening, editing, or downloading it.
Proposed solution
Show the result location when the user hovers over a search result row or filename. The tooltip should display the relative parent path of the result, using the existing search result path data if available.
This should be possible as a frontend-only change if the current search response already includes the full path for each result. If the backend does not provide enough path information in some cases, the issue should document the missing field before adding backend work.
Acceptance criteria
Problem
Cloud search results can show multiple files with similar or hash-like names. The list currently makes it hard to understand where a search result is located without opening or interacting with it further.
Example scenario:
Proposed solution
Show the result location when the user hovers over a search result row or filename. The tooltip should display the relative parent path of the result, using the existing search result path data if available.
This should be possible as a frontend-only change if the current search response already includes the full
pathfor each result. If the backend does not provide enough path information in some cases, the issue should document the missing field before adding backend work.Acceptance criteria
SearchResultDto.pathdata where available./.