Identifiers

8 pages filed under Rules › Identifiers. A business rule is a condition the business imposes, with what it constrains and what happens when it is broken.

Business rule	Severity	First line	Links
Relation outside the matrix	error	A declared relation joins two types the profile does not allow for it. The link is dropped from the model by the relation typing step. A frontmatter reference that names an existing note of a type the attribute does not accept is this finding, not an unresolved reference: the note exists, the relation is what the profile forbids.	38
Invalid identifier	error	A frontmatter id does not follow the identifier pattern, lowercase letters, digits and hyphens in a first segment, then at least one more segment after a slash. The declared value is ignored and the identifier derives from the source name and the file path, as if no id had been written, so that the page still exists at a predictable address; the finding says which value was refused.	18
Invalid encoding	error	A file is not valid UTF-8, a note saved in a single-byte encoding for instance. The file is skipped entirely: nothing of it enters the model, and every link that points to it is reported as a broken link. The linter reports it before the file is pushed, and an .editorconfig with charset = utf-8 keeps the mistake from coming back.	17
Duplicate identifier	error	Two files resolve to the same identifier, because identifiers strip the extension and the type suffix, or because two notes declare the same id. The first in canonical order is kept.	14
Type conflict	error	The frontmatter type contradicts the type given by the file suffix. The tool reports rather than guesses.	13
Invalid frontmatter	error	The YAML frontmatter cannot be parsed. The body is still processed; every declared attribute is lost.	12

6 identifiers of 6 — pagination by twenty. The Links column counts the related pages, which brings the most central identifiers of the journey to the top.