docx-validate
    Preparing search index...

    Function relationshipTargetPartName

    • The package-relative part name one relationship target references, resolved against baseDir, the folder of its source part, as the rest of the codebase does (\ reads as /, a query or fragment is dropped, dot segments resolve, a package-absolute reference resolving the path below its leading / against the package root the same way and keeping the / (#947)): undefined for a target with a URI scheme or an empty reference. The path resolves as path.posix.join resolves it, so, unlike RFC 3986, an empty segment collapses: word//main.xml names word/main.xml, as Word read it (session 70, #962). A final . or .. segment leaves a folder, which keeps the final / RFC 3986 gives it and path.posix.join would drop: word/main.xml/. and word/main.xml/x/.. name word/main.xml/, which Word refused as a part (session 70, #962); the package root keeps its own spelling, . or /. The target's .. segments stop at the package root instead of climbing past it, a package-absolute reference's climb and a final bare .. included (#962), as RFC 3986's remove_dot_segments stops them and as Word read every such target it was shown: word/'s ../../footnotes.xml named /footnotes.xml (sessions 63, 64 and 74, #830), and so did the styles, header, customXml, comments and officeDocument climbs of sessions 75 to 78 (#984, #986).

      Parameters

      • baseDir: string
      • target: string

      Returns string | undefined