mirror of
https://github.com/mbierlee/poodinis.git
synced 2024-11-15 04:04:01 +01:00
Remove known, unsolvable, issue
Any logical solution would endlessly autowire new instances if no stop condition is given. The current circular dependency resolution system provides such a stop condition just fine.
This commit is contained in:
parent
5caf57d31d
commit
50824b4e5c
|
@ -123,7 +123,6 @@ Poodinis can autowire circular dependencies when they are registered with single
|
||||||
|
|
||||||
Known issues
|
Known issues
|
||||||
------------
|
------------
|
||||||
* Due to preventive measures of recursion issues in circular dependencies, registrations which are supposed to yield new instances will not autowire classes for which a circular dependency is detected. A new instance will be resolved but the instance's members will not be autowired.
|
|
||||||
* Resolving a class registered by supertype or interface will only autowire the members inherited from its supertypes and in the case of interfaces none at all. A workaround for this issue is to autowire members in the constructor of a class:
|
* Resolving a class registered by supertype or interface will only autowire the members inherited from its supertypes and in the case of interfaces none at all. A workaround for this issue is to autowire members in the constructor of a class:
|
||||||
```d
|
```d
|
||||||
import poodinis.autowire;
|
import poodinis.autowire;
|
||||||
|
|
Loading…
Reference in a new issue