topmark.resolution package index¶
topmark / resolution
Input, file type, and processor resolution utilities.
The topmark.resolution package contains helpers that
answer two related runtime questions:
- which filesystem paths TopMark should process;
- which
FileTypeand boundHeaderProcessorapply to each resolved file.
Conceptually, this package sits between the registry and the pipeline:
- Registry layer (
topmark.registry) Maintains the composed registries of file types and header processors. - Resolution layer (
topmark.resolution) Resolves concrete inputs, file types, and processor bindings. - Pipeline layer (
topmark.pipeline) Orchestrates processing steps and updates the processing context.
The resolution logic is intentionally separated from the pipeline so it can be reused independently by tooling, tests, and future APIs.
Current module roles:
topmark.resolution.filesdecides which files should be processed by expanding configured inputs and applying path-based and file-type-based filters.resolve_file_list()- determine the concrete input files to process.probe_resolution_for_path()- explain file type and processor resolution for a path.get_file_type_candidates_for_path()- inspect all candidate file type matches and their scores.
Typical entry points include:
resolve_file_list()- determine the concrete input files to process.get_file_type_candidates_for_path()- inspect all candidate file type matches and their scores.
These helpers respect optional include/exclude file type filters, allowing callers to constrain resolution when required.
Immediate children in this package¶
- topmark.resolution.discovery
- Discovery-level probe results for explicit input selection.
- topmark.resolution.files
- Resolve the concrete filesystem inputs that TopMark should process.
- topmark.resolution.filetypes
- Path-based file type and processor resolution helpers.
- topmark.resolution.probe
- Probe result contracts for file type resolution diagnostics.