-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for getting interfaces in OnReadyGet #30
Comments
Interesting... yeah, it would make sense to allow this, and it's a pretty simple change. A potential issue is that For example, it's impossible to tell whether
That said... I think it's safe for If someone does run into the limitation caused by the assumption, there are ways out. The easiest would be to add a bool arg onto the attribute that indicates the target should be a resource. So, I think it's fine to relax this requirement and make this assumption. |
I've released 1.1.3 that includes this change, let me know if it doesn't end up working for you! Thanks for the suggestion. |
It would be useful if we could use OnReadyGet to initialize an interface field with a reference node. Game engines like Unity include this feature in their
GetComponent<T>()
function.The text was updated successfully, but these errors were encountered: