Package network.ike.docs.plugin.registry


package network.ike.docs.plugin.registry
  • Class
    Description
    Every .adoc file under a registry root with the git blob id of its content: the key the incremental registry decides staleness by (dev-adoc-packages, IKE-Network/ike-issues#1341).
    Where a BlobIndex took its blob ids from.
    Read a BlobIndex from git without opening a file (dev-adoc-packages, IKE-Network/ike-issues#1341).
    The blob-keyed incremental registry (dev-adoc-packages, IKE-Network/ike-issues#1341).
    What one update did.
    The term index IKE-INDEX.md and IKE-TOPIC-REGISTRY.md describe, term-index.yaml: the reverse mapping from the index terms a topic marks (indexterm:[primary, secondary], indexterm2:[term], ((term)), (((primary, secondary)))) to the topics that mark them.
    The parsed header of one AsciiDoc file: the :topic-*: attribute block, the anchor and the level-1 heading, read line by line without AsciidoctorJ.
    The generated topic registry: every AsciiDoc file under a scan root, parsed by TopicHeader, in the shape IKE-TOPIC-REGISTRY.md gives topic-registry.yaml: topics grouped into domains by the prefix of their id, each with the registry's field names (id, file, title, type, keywords, status, char-count, related, summary), then what a build can add on top: assemblies and plain files with their document attributes, the findings the headers raise, and a generation stamp.
    One scan root's result.