feat(#288) add register_geometry_yaml in-memory registration entry point#289
Merged
Conversation
In-memory companion to register_geometry_file: takes a YAML string and a required name, eagerly validates the schema, installs a closure-bound factory that re-parses the captured text on each make_geometry() call. Exported at Tier 1 in __init__.py alongside register_geometry_file. Contributed by: OpenCode (argo/claudeopus47)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In-memory companion to
register_geometry_file: takes a YAML stringand a required
name=, eagerly validates the schema, and installs aclosure-bound factory that re-parses the captured text on each
make_geometry()call (mirroring the per-call re-read semantics ofregister_geometry_file). Duplicate-name registration raisesValueError, matching the existing contract.Exported at Tier 1 in
__init__.pyso it sits alongsideregister_geometry_filein the public API.Tests cover: required-
namecontract, registry round-trip viamake_geometry(), duplicate-name guard, eager schema validation,and per-call re-parse. Full suite: 2580 passed, 100% coverage.
Contributed by: OpenCode (argo/claudeopus47)