Interface RefusedExportTrace

A trace an export left out. Nothing was written for it.

interface RefusedExportTrace {
    id: string;
    field: "type" | "path" | "id" | "scope";
    problem: "outside" | PathNameProblem | "link" | "special" | "collision";
}

Properties

Properties

id: string

The trace's id, as stored.

field: "type" | "path" | "id" | "scope"

The value that was refused: the trace's scope, type or id, which name its folders and its file in a Markdown or Obsidian export; or path, the trace's place in the export folder as a whole.

problem: "outside" | PathNameProblem | "link" | "special" | "collision"

Why: for a scope, type or id, the part of the name rule the value breaks (PathNameProblem in core/utils/pathName); for a path, outside when the path an exporter subclass builds lies outside the export folder, link when a folder or file in the trace's place under the export folder is a symbolic link or the file has a second name (a hard link), since the export never writes through a link, special when something other than a regular file holds the file's place (a folder, a named pipe, a socket, a device), which the export never writes to or waits on, and collision when an older trace's file is the same file: where names differ only in case or Unicode form, which macOS and Windows treat as one name, or where the file system makes two names one file in another way, such as a Windows short name.