Skip to content

Resolve the processor registry on either relaton line - #132

Merged
ronaldtse merged 1 commit into
lutaml-integrationfrom
fix/relaton-v3-registry
Sep 16, 2026
Merged

ronaldtse merged 1 commit into
lutaml-integrationfrom
fix/relaton-v3-registry

Conversation

@ronaldtse

Copy link
Copy Markdown
Contributor

relaton v3 moved the top-level Relaton::Registry to Relaton::Db::Registry (same surface: processors, by_type, find_processor_by_dataset). Every CLI call site now resolves through Relaton::Cli.registry — v3 constant first, v2 fallback — so the CLI runs against both lines.

Without this, site generation under the v3 monogem crashes at the collection step:

lib/relaton/cli.rb:107:in 'get_proc': uninitialized constant Relaton::Registry (NameError)

(reproduced building mn-samples-iala with the v3 stack.)

relaton v3 moved the top-level Relaton::Registry to Relaton::Db::Registry
(the Db singleton registry with the same processors/by_type/
find_processor_by_dataset surface). Every CLI call site now goes through
Relaton::Cli.registry, which resolves the v3 constant first and falls
back to the v2 constant, so the CLI works with both released v2 and the
v3 monogem (site generation crashed with 'uninitialized constant
Relaton::Registry' under v3).
@ronaldtse
ronaldtse merged commit de7f382 into lutaml-integration Sep 16, 2026
11 checks passed
ronaldtse added a commit that referenced this pull request Sep 25, 2026
The dependency floor becomes relaton >= 3.0.0.pre.alpha (the monogem)
and Relaton::Cli.registry resolves Relaton::Db::Registry directly —
the v2 fallback stays on the 2.x line (PR #132).
ronaldtse added a commit that referenced this pull request Sep 25, 2026
The dependency floor becomes relaton >= 3.0.0.pre.alpha (the monogem)
and Relaton::Cli.registry resolves Relaton::Db::Registry directly —
the v2 fallback stays on the 2.x line (PR #132).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant