Unify Handlers via Adapter Interfaces (Future-Proof) #2
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.
Please drop all related feedback into the source PR for having everything in the same place
Key improvements in this extended branch of PR Unity-Technologies#3430
INetworkPrefabInstanceHandlerSource
: Common abstraction for all handler types, exposing a consistent adapter regardless of instantiation dataINetworkPrefabInstanceHandlerAdapter
: Centralizes the instantiation flow under a single contract, removing the need for branching based on handler typeAdapter-based routing
INetworkPrefabInstanceHandler
,INetworkPrefabInstanceHandlerWithData<T>
,future variants...
) now expose an adapter viaINetworkPrefabInstanceHandlerSource
AddHandler
now operate via the unified interfacesCompatibility adapters
LegacyHandlerAdapter
andPrefabInstanceHandlerWithDataAdapter
wrap existing implementations without changing their internal behavior, for backwards compatibility