-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Migrate openResult method to SearchResult component #41785
Conversation
86cf466
to
3f4a7a2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this element should be a real link
@ChristophWurst using the |
Then the component needs a new prop to influence this behavior |
@ChristophWurst that makes sense, I have created these issue for that here : nextcloud-libraries/nextcloud-vue#4880 and here #41800 Because this breaks search entirely, so this PR should restore the old initial before of using JavaScript to trigger the routing. |
3f4a7a2
to
0710327
Compare
/backport to stable28 |
0710327
to
5220d89
Compare
/compile amend / |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works for simple clicks again
The approach of window.location is still there and problematic
5220d89
to
b0e4c0c
Compare
ab654cb
to
f639997
Compare
/compile amend / |
After moving the `SearchResult` to its own component and leaving out the openResult method, the search results do not lead anywhere but but error out. Signed-off-by: fenn-cs <fenn25.fn@gmail.com> Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
f639997
to
00bb1bc
Compare
Ref #41381 (comment)
After moving the
SearchResult
to its own component and leaving out theopenResult
method, the search results do not lead anywhere but but error out.