Add asset server untyped handles#336
Merged
waynemwashuma merged 3 commits intoJun 7, 2026
Merged
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.
Objective
Introduce untyped asset loading APIs for type-erased asset restoration and improve asset handle snapshot serialization by storing asset type IDs instead of constructors.
Solution
HandleSnapshotpreviously stored a constructor reference and relied on recovering the corresponding type ID during deserialization. This created an unnecessary dependency on runtime type objects and made snapshots less suitable for serialization and type-erased workflows. This changes snapshots to store the asset type ID directly and adds an untyped asset loading path toAssetServer.Why this approach:
Showcase
New type-erased loading is available:
Migration guide
No migration required
Notes
loadUntyped()primarily exists for serialization, reflection, editor, and tooling workflows.Checklist