mirror of
https://github.com/bulwarkmail/webmail.git
synced 2026-10-31 00:12:39 +00:00
Linus Rath
d9ffe8a76e
Fixes from the review of the Files work (1cf9944b..a9a25b94).
- A file shared on its own, or one below a folder its owner took back,
could not be reached. Once Stalwart 1.0's placeholder folders were
left out it became a root of "Shared with me", which listed folders
only, and search opened it on the drive root. 0.16 lists such files
as roots too. Each owner's files shared on their own are now listed
on one page under "Shared with me" ("Files from <name>"), where they
open, preview and download like any other file and nothing can be
added; two of the same name get a number. Search opens a shared hit
where it is listed, and links into a shared drive name the node by id
(`/files?shared=<owner>:<id>`), so a shared folder or page also
survives a reload. A Files page that is already open takes the link
from search directly, since Next keeps it mounted when only the query
changes.
- A copy that fails part-way destroys only the nodes it made, the
deepest first and without `onDestroyRemoveChildren`, one call per
level because 0.16 refuses a folder destroyed in the same call as
its children. It used to destroy the new folder with everything
below it, so whatever someone put there during a long copy was
deleted for good. A folder holding such nodes now stays, and the
error says part of the copy was left in place.
- The document editor opens read-only on 0.16 for a sharee without the
rename right. 0.16.6 to 0.16.23 refuse any change a sharee makes
without Modify, so every save of such a document failed with a 500.
1.0, told apart by its `maxFileNodeDepth`, still asks for
`mayModifyContent` alone.
- Ctrl+C with only symlinks selected empties the clipboard instead of
keeping an earlier cut for the next paste.
- A paste reads each account's file tree once, not once per pasted
item for the listing and 1.0's depth check.
- The Stalwart bundle's README says that on older 0.16 releases and
the 1.0 pre-releases a failed update also drops the cached copy, and
the next restart or reload of the Applications downloads it again,
not only a later `UpdateApps`. The static README says a restart
applies the CORS setting on the current 1.0 pre-releases, where
`ReloadSettings` fails with the stock spam-filter rules.
63 lines
2.3 KiB
TypeScript
63 lines
2.3 KiB
TypeScript
import { jmapError, jmapErrorProperties, jmapErrorType, type JmapError } from '@/lib/jmap/jmap-error';
|
|
|
|
/**
|
|
* Why a FileNode write failed, from the SetError the JMAP client threw
|
|
* (see jmapError), for the Files toasts to explain under their own title.
|
|
*/
|
|
export type FileErrorKind = 'overQuota' | 'tooDeep' | 'invalidName' | 'forbidden' | 'tooLarge';
|
|
|
|
// Stalwart 1.0's description for a node past maxFileNodeDepth.
|
|
const TOO_DEEP = 'Maximum folder depth exceeded.';
|
|
|
|
/** The error for a node that would sit deeper than the server allows, worded as Stalwart 1.0 does. */
|
|
export function folderDepthError(): Error {
|
|
return jmapError(TOO_DEEP, { type: 'invalidProperties', properties: ['parentId'] });
|
|
}
|
|
|
|
type PartialCopyError = JmapError & { partialCopy?: boolean };
|
|
|
|
/**
|
|
* The error for a copy that stopped part-way and could not be taken back
|
|
* completely, so part of it is still there. It keeps the message and JMAP
|
|
* type of `cause`, which say why the copy stopped.
|
|
*/
|
|
export function partialCopyError(cause: unknown): Error {
|
|
const message = cause instanceof Error ? cause.message : String(cause);
|
|
const error: PartialCopyError = jmapError(message, {
|
|
type: jmapErrorType(cause),
|
|
properties: jmapErrorProperties(cause),
|
|
});
|
|
error.partialCopy = true;
|
|
return error;
|
|
}
|
|
|
|
/** Whether a failed copy left part of itself in place (see partialCopyError). */
|
|
export function isPartialCopy(error: unknown): boolean {
|
|
return (error as PartialCopyError | null | undefined)?.partialCopy === true;
|
|
}
|
|
|
|
export function fileErrorKind(error: unknown): FileErrorKind | null {
|
|
switch (jmapErrorType(error)) {
|
|
// Stalwart 1.0, once an administrator limits files or folders per account.
|
|
case 'overQuota':
|
|
return 'overQuota';
|
|
// 1.0 for content over 4 GiB.
|
|
case 'tooLarge':
|
|
return 'tooLarge';
|
|
case 'forbidden':
|
|
return 'forbidden';
|
|
case 'invalidProperties': {
|
|
const properties = jmapErrorProperties(error);
|
|
if (properties.includes('name')) return 'invalidName';
|
|
// `parentId` is refused for other reasons too (the folder is gone, a
|
|
// folder moved into itself); only the description tells depth apart.
|
|
if (properties.includes('parentId') && error instanceof Error && /depth/i.test(error.message)) {
|
|
return 'tooDeep';
|
|
}
|
|
return null;
|
|
}
|
|
default:
|
|
return null;
|
|
}
|
|
}
|