-
-
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
Use href & target attribute for NcListItem in search result #41800
Labels
Comments
3 tasks
nfebe
added a commit
that referenced
this issue
Dec 6, 2023
Following the update of `NcListItem` to allow control over where and how passed `hrefs` open, the search result component can now make use of these props. See : nextcloud-libraries/nextcloud-vue#4923 Resolves : #41800 Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
nfebe
added a commit
that referenced
this issue
Dec 6, 2023
Following the update of `NcListItem` to allow control over where and how passed `hrefs` open, the search result component can now make use of these props. See : nextcloud-libraries/nextcloud-vue#4923 Resolves : #41800 Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
backportbot-nextcloud bot
pushed a commit
that referenced
this issue
Dec 6, 2023
Following the update of `NcListItem` to allow control over where and how passed `hrefs` open, the search result component can now make use of these props. See : nextcloud-libraries/nextcloud-vue#4923 Resolves : #41800 Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
zak39
pushed a commit
to zak39/server
that referenced
this issue
Dec 19, 2023
Following the update of `NcListItem` to allow control over where and how passed `hrefs` open, the search result component can now make use of these props. See : nextcloud-libraries/nextcloud-vue#4923 Resolves : nextcloud#41800 Signed-off-by: fenn-cs <fenn25.fn@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug description
Use href of
NcListItem
once nextcloud-libraries/nextcloud-vue#4880 is completed.The text was updated successfully, but these errors were encountered: