MonoBehaviour/Components injection issues

[Jo Simard]

Hi,
we had problems troubleshooting injection issues when requesting bindings with components.

Unity did throw some warning, but the stack made it hard to troubleshoot:

You are trying to create a MonoBehaviour using the 'new' keyword. [...]

An error should be implemented to help users pin-point the issue fast. The issue can happen often when using injection with components, either when component values are null or when the binding order is wrong.

I managed to implement an error message that greatly helps finding from which components are problematic:
josimard@21cab92

Ultimately, we did not find how to specify the injector not to instantiate some types... It was hard understand why we had multiple instances of our behaviors when using injection at first. We are not sure why the binding order is so important in our case...

This is how we bind component instances in our container:

container.Bind<T>().To(instance);

[André "Intentor" Martins]

Thanks for the feedback and solution!

I'll look into the issue and analyse your solution to incorporate it on an official release.

[Jo Simard]

Hi André,
Thanks for considering,

Alternatively, do you know of a way we could prevent the injector to instantiate,
that it would return null without an instance binding?

[André "Intentor" Martins]

Currently, there's no way to do that. Adic will always try to instantiate. However, that can be developed!

I opened the issue #46 to develop this new feature.

[moathlowahi]

It's not because "Adic will always try to instantiate", it's because there is a goddman fucking bug in the code!
File: Binder.cs || Line: 58
"this.AddBindingToDictionary(new BindingInfo(valueType, valueType, BindingInstance.Singleton));"
Should be:
"this.AddBindingToDictionary(new BindingInfo(valueType, binding.value, BindingInstance.Singleton));"

[André "Intentor" Martins]

Hello @moathlowahi!

Thanks for your reply. I'll check and incorporate it on the next release!

However my answer to @josimard remains correct and the issue #46 added the feature he commented about, as described on https://github.com/intentor/adic#instance-resolution-modes.

The code you used as example for the issue is part of the feature added on #46. A singleton of the value being added is always added to the container regardless of the binding type, so it can be reused inside the container, keeping it singleton (as described on #44).

[moathlowahi]

Before changing that piece of code, whenever you try bind a Singleton as an Instance for the first time to another interface, Adic will try to instantiate it, but this is wrong since that Singleton is provided as an Instance in this case. To reproduce this effect you can do something like this:
myContainer.Bind<IWhateverInterface>().To<MyMonoBehaviour>(FindObjectOfType<MyMonoBehaviour>());

You will get the following error:

You are trying to create a MonoBehaviour using the 'new' keyword. [...]

N.S: This is not because of FindObjectOfType<MyMonoBehaviour>() returning null or any other silly coding mistake.

[André "Intentor" Martins]

Hello, @moathlowahi!

Thanks for your contribution! I've already been able to reproduce the issue and a fix has been pulled. It'll be available on the version released later next week.

[André "Intentor" Martins]

The pull request #64 added better descriptive messages.

This issue will be closed.