Skip to content

Project current registered configuration declarations for readiness - #9

Merged
trissim merged 1 commit into
mainfrom
perf/registered-schema-readiness-20261003
Oct 3, 2026
Merged

trissim merged 1 commit into
mainfrom
perf/registered-schema-readiness-20261003

Conversation

@trissim

@trissim trissim commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Expose LazyDataclassFactory.registered_type_pairs() as a fresh tuple projected directly from the existing lazy/public type mapping. OpenHCS readiness uses this to prepare current configuration declarations after callable hooks, including late registrations when the callable catalog is already cached. No configurations or default factories are evaluated and no second roster is retained.

Validation: all 25 existing lazy-factory tests pass; 119 OpenHCS preparation/catalog/startup tests pass with the new consumer test covering late registration, both public/proxy declarations, non-dataclass filtering, pre-READY ordering and zero factory evaluation.

Consumer: OpenHCSDev/openhcs#394

Closes #8

Copilot AI balanced review requested due to automatic review settings October 3, 2026 04:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

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.

Expose registered lazy/public type pairs for configuration readiness

2 participants