Fix: Instantiation of a MonoBehaviour doesn't inject the entire instantiated GameObject #452
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.
When we pass a component to the
Object.Instantiate
, the Unity actually instantiates the entire GameObject that the MonoBehaviour belongs to. The returned MonoBehaviour instance actually attaches to a newly spawned GameObject which requires injection (initialization) also.This patch fixes the issue that
T Instantiate(IObjectResolver resolver, T prefab ...)
series functions don't inject the entire spawned GameObject if a non-GameObject T is provided.