mirror of
https://github.com/mbierlee/poodinis.git
synced 2024-11-15 04:04:01 +01:00
Add workaround to readme
This commit is contained in:
parent
47d7f72fae
commit
7afefd9d9c
13
README.md
13
README.md
|
@ -124,7 +124,18 @@ 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.
|
* 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.
|
* 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
|
||||||
|
class ComponentF {
|
||||||
|
@Autowire
|
||||||
|
public ComponentA componentA;
|
||||||
|
|
||||||
|
public this() {
|
||||||
|
auto container = Container.getInstance();
|
||||||
|
container.autowire!ComponentF(this);
|
||||||
|
}
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
Future Work
|
Future Work
|
||||||
-----------
|
-----------
|
||||||
|
|
Loading…
Reference in a new issue