Draft
Conversation
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
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.
Summary
Adds a
default_materializerargument toRegistry/_RegistryCoreso users can opt into a fallback serializer (e.g. ZenMLCloudpickleMaterializer) when no type-specific materializer is registered.This enables saving/loading callables and custom classes without first registering explicit materializers for each type.
Closes #309
What changed
default_materializerto:Registry.__init___RegistryCore.__init___find_materializerto include registry-level fallback:default_materializerfallbackUsage examples (verified)
I ran these examples locally on this branch and confirmed they execute successfully.
Testing
pytest -q tests/unit/mindtrace/registry/core/test_registry.py -k "default_materializer or save_without_materializer"ds test --unit(full unit suite on branch)