You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The mime test becomes canView(node), which asks the registered handlers rather than a
flattened mime list. open() takes @nextcloud/files nodes rather than a path, so either build
the node or hand openFolder(folder, file) a folder and let it fetch.
OCA.Viewer is gone in Viewer 7.0.0. The viewer ships as the @nextcloud/viewer library rather than a
bundled app, and nextcloud/server#63954 removes the viewer app from Nextcloud 36 altogether.
Roughly what it looks like:
import{canView,getViewer}from'@nextcloud/viewer'// OCA.Viewer.open({ path }) / ({ fileInfo, list })getViewer().open(nodes,file)// @nextcloud/files nodesgetViewer().openFolder(folder,file)// when a path is all you have, let it fetch// OCA.Viewer.mimetypes.includes(mime) / availableHandlerscanView(node)
The part that is not a rename is that the viewer takes @nextcloud/files nodes now, not fileinfo objects or path strings. Importing the package is also all it takes to get the viewer
onto the page: no LoadViewer event to dispatch, and nothing to check about whether the app is
enabled.
Important
There is no compatibility shim, which was a deliberate call, so this is a real port rather
than a rename. Nothing breaks until the server PR lands; after that these calls throw on
Nextcloud 36.
Recommendations opens a recommended file in the viewer:
src/components/RecommendedFile.vue:135:window.OCA.Viewer.mimetypes.indexOf(props.mimeType) !== -1src/components/RecommendedFile.vue:136:window.OCA.Viewer.open({ path: path.value })The mime test becomes
canView(node), which asks the registered handlers rather than aflattened mime list.
open()takes@nextcloud/filesnodes rather than a path, so either buildthe node or hand
openFolder(folder, file)a folder and let it fetch.OCA.Vieweris gone in Viewer 7.0.0. The viewer ships as the@nextcloud/viewerlibrary rather than abundled app, and nextcloud/server#63954 removes the
viewerapp from Nextcloud 36 altogether.Roughly what it looks like:
The part that is not a rename is that the viewer takes
@nextcloud/filesnodes now, notfileinfoobjects or path strings. Importing the package is also all it takes to get the vieweronto the page: no
LoadViewerevent to dispatch, and nothing to check about whether the app isenabled.
Important
There is no compatibility shim, which was a deliberate call, so this is a real port rather
than a rename. Nothing breaks until the server PR lands; after that these calls throw on
Nextcloud 36.
Tip
The developer manual covers the migration under
Critical changes
(being added in nextcloud/documentation#15597), and the
README
has the full before/after table. Happy to help with the port, just ping me.
👾 This issue was written with the help of Claude Code.