erlef / purl / 2323e5ffca5b65ad95d452241eeb98ed09ec7a35

86%

Build Type

push

github

Committed by web-flow

Commit Message

Compile purl type specifications into a generated module (#152)

The type registry cached the purl-spec type definitions in a DETS table
under priv/data. That requires a writable priv directory, which is not
available in a typical production release, and made the JSON specs a
runtime dependency.

Instead, generate src/purl_type_data.erl from priv/spec/types/*.json at
build time and commit it. The registry now seeds its ETS table from that
module, so ETS keeps behaving exactly as before while startup no longer
touches the filesystem.

Generation lives in a rebar3 plugin (rebar3_purl_gen) under _checkouts so
that rebar3 loads erlfmt for it, which keeps the generated file compliant
with `rebar3 fmt --check` and makes `--check` a plain byte comparison. The
generated header records the purl-spec revision it was built from.

Run `rebar3 purl_gen` after bumping the priv/spec submodule and commit the
result. CI runs `rebar3 purl_gen --check` to keep the two in sync.

Since the definitions are compiled in, priv/spec/types is no longer
published to Hex; the spec LICENSE is still shipped as the data is derived
from it.

Note: the `type_dir` start option is removed, as types no longer load from
disk.

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Coverage Stats

6 of 7 new or added lines in 2 files covered. (85.71%)

17 existing lines in 1 file now uncovered.

411 of 478 relevant lines covered (85.98%)

75927.62 hits per line