Fix for some Exceptions and Support for AssetReferenceT<> #2
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
sadegh-askari
changed the title
… matching component without this fix if property name does not contain prefab and there isn't any matching component in the scene, component assigner leaves the field as null!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
I ran into these problems and I fix them on my fork:
InvalidCastException: if call Auto Assign on ScriptableObject to find Prefabs that their property name not contains 'prefab'
InvalidCastException when use auto assign on ScriptableObject #1 (comment)
NullReferenceException on prefab provider
and also I implemented support for AssetReferenceT<>