PathCompatibilityViolationType
What a single path or name is wrong about, on one platform.
Import:
import type { PathCompatibilityViolationType } from '@mnaoumov/obsidian-lib/path-compatibility';Signature:
export enum PathCompatibilityViolationTypeMembers:
| Member | Value | Description |
|---|---|---|
ForbiddenCharacter |
'ForbiddenCharacter' |
|
NameTooLong |
'NameTooLong' |
|
ObsidianForbiddenCharacter |
'ObsidianForbiddenCharacter' |
The name holds a character Obsidian links do not work with (#, ^, [, ], |). Obsidian’s rule, not a platform’s: the filesystem stores such a name fine, so naming a platform for it would be false. |
PathTooLong |
'PathTooLong' |
|
ReservedName |
'ReservedName' |
|
TrailingCharacter |
'TrailingCharacter' |
|
UnicodeNotNormalized |
'UnicodeNotNormalized' |
The name is stored on disk in a form other than Unicode NFC, e.g. й as и followed by a combining breve. Not a platform’s rule but a sync hazard: tools outside Obsidian see the two forms as two names. |
Links to this page: