Skip to content

just_dna_compiler.compiler.check_paths

just_dna_compiler.compiler.check_paths

Which path asks each check: the roster behind validate/compile parity (RM367).

validate_spec is the pre-flight for compile_module, and the contract between them is one verdict and one set of findings (@validate-refuses-all, @parity-by-check). A check is normally asked on both paths. This module names the ones that are not, each with its reason, and compiler/tests/test_check_paths.py walks the two function bodies and asserts the roster as an equality against what they call: a check added to one path and not the other fails the walk until it is either asked on the other path too or entered here with a reason.

The pre-flight-only side is large and needs no reason per entry: compile_module runs the pre-flight first, in its own mode, refuses on its errors and seeds its warning channel from its findings, so a check asked only there reaches the compile's result without being asked twice. The compile-only side is where a reason is owed, and it is meant to stay short.

The one exemption the walk cannot see. The deprecated ensembl_cache path (removed at 1.0) resolves rows against a reference the pre-flight is never handed, so what follows from that resolution — coverage, the strict aggregate, the resolved-row cross-checks — is the compile's alone on that path (_validate_spec(legacy_reference=True), which then skips those judgements rather than ask them over unresolved rows). It is a reference, not a check, so it has no name to walk.