RegistryMixin - tooling for easier registry/plugin patterns across NM repos #365
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.
proposes a structure that can be used as a universal registry for NM parent classes that follow a registry pattern or future plugins
Classes or factories that require a registry can add
RegistryMixin
as a parent class to get access to the functionality. The included classmethods should work for each class that contains the mixin separately.Supports either loading values either from the registered names or a
file:name
pattern for custom file impelementations.brief example from doc
test_plan:
simple unit tests included