markdown_links.ts

Directory names the file index never enters, wherever they appear under a root — the backend filer's default ignores (DEFAULT_IGNORED_DIRS in crates/zzz_server/src/filer.rs, which a test holds this to). A link into one is skipped, not broken.

The prefix of the backend's staging files, which the index never lists (TEMP_FILE_PREFIX in crates/zzz_server/src/scoped_fs.rs, which a test holds this to).

The names a folder link opens, first found wins — a repository host shows the README.

A heading in a markdown document, for an outline.

A link in a markdown document, resolved.

What the file index knows — the files and folders under its roots — for telling a link's target exists, is missing, or is out of sight.

How the preview marks a link: broken when the index says its target is missing, unknown when the index can't see where it points.

How a path link stands against the file index:

• file / directory — it names an indexed file, or a folder holding one
• broken — it's inside a root the index covers, where the index would list it, yet nothing is there
• the index can't say (see MarkdownLinkMark's unknown):
  • outside — outside every root the index covers
  • skipped — inside a folder the index never enters (FILE_INDEX_IGNORED_DIR_NAMES)
  • root_relative — written /… and not found from the workspace's root, which may not be the repository's

Where a link in a markdown file leads:

• external — an http: or https: URL, left to the browser
• fragment — a heading in the same document (#id, decoded)
• path — an absolute path on disk, with directory when the link names a folder (a trailing /, or a last segment of . or ..), its decoded #fragment if any, and root_relative when it was written /…
• inert — nothing to follow: empty, query-only, another scheme, protocol-relative, malformed, climbing past its root, or relative with no file to resolve against

The rendered <a> of each of links inside container, matched by document order — the ith anchor with an href is the ith link — or null when the counts disagree, so no link is paired with another's anchor. Order, not href, because the href isn't always the reference: mdz renders a root-relative one through SvelteKit's resolve, collapsing its leading run of / and \ to one / (//a/b.md renders /a/b.md), so an anchor that reads as a path can stand for a reference this module reads as protocol-relative or backslashed, and inert. Assumes mdz renders every anchor in container, which holds while no mdz context injects components that render their own.

Resolves href, a link's reference in a markdown file, to where it leads (see MarkdownLinkTarget). A path link drops its ?query, keeps its #fragment, has each segment percent-decoded, and is normalized: . and empty segments vanish and .. climbs, but never above / — or above root_dir for a root-relative link — which makes it inert. An escape that decodes to / or a NUL is inert too, since it would change the path's shape.

The README a link to the folder at dir_path opens, or null when the index has none there (see MARKDOWN_DIRECTORY_INDEX_NAMES).

The document's headings in rendered order, those in blockquotes included — the ith is the preview's ith h1–h6.

The mark for a link with status, or null for one that needs none.

Checks a path link's target against the file index (see MarkdownLinkStatus). A folder holding no indexed file — say an empty one — reads as missing, since the index lists only files.

The title a link shows on hover to say how it stands, or null for a link that needs none.

The document's links that render as <a> elements (mdz renders an unsafe reference as plain text), in rendered order, each resolved against file_path and checked against index. A root-relative link resolves against the innermost of the index's roots holding the file.

The plain text of nodes, formatting dropped.

The innermost of roots (directories with a trailing /) holding path, or null when none does — the directory a root-relative link in the file at path resolves against.