Register component clone and copy into type registry#309
Merged
waynemwashuma merged 2 commits intoMar 29, 2026
Conversation
clone and copy into type registry
614d7dc to
b199eec
Compare
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.
Objective
Integrate
copy/clonesemantics into the type registry system.Typeinfomethod registration #307Solution
Although
copy/clonemethods were introduced on components, they were not discoverable through the type registry. This adds a way to use the type registry to clone/copy components in reflection based systems without needing to know the underlying type.Changes made
Added method registrations for
``copyandcloneacross all registered component types.Why this approach
copy/clonewithout hardcoding typesShowcase
Before
After
Migration guide
No migration required.
Checklist