T
Size: a a a
2020 June 16
AM
Still the same thing: https://github.com/yii-extension/framework-bundle/blob/master/composer.json#L22
T
An alternative may be to create a repository and merge the configurations, but the yi packages should use the yii container which already depends on other yii packages.
T
yii-web would not work with another container
AM
TradersVE
yii-web would not work with another container
That's the main question if it should.
T
How would you use yii-web outside the framework?
AM
It is not yii-web outside of the framework. It is different PSR container with Yii.
T
It is not yii-web outside of the framework. It is different PSR container with Yii.
If I understand that but in yii packages using another container is not going to guarantee that the package works completely since it depends indirectly on the implementation of our container
AM
Even if only get() and type-hints are used?
AM
We're not doing set() anywhere except providers
T
Would it be possible to separate Service Provider, and make it use ContainerInterface, and be compatible with container league?
T
Container League also support Service Provider
AM
unlikely
AM
ContainerInterface isn't enough for provider
AM
because ContainerInterface doesn't have any setter methods
T
But Service Providers two methods boot and register
В
I think optional container is a good way to increase the frameworks audience. Some people are really like containers written by the League and Symfony. It will be difficult for them to understand how to use functionality of factory or subcontainers in our implementation. And they don't need to if they can use what they used to use before.
So I'm for container-agnostic libraries.
So I'm for container-agnostic libraries.
NO
It it does more than what is defined in PSR, it is not interchangeable with PSR-compatible containers )
So the question is, should framework components be compatible with any PSR container?
So the question is, should framework components be compatible with any PSR container?
NO
Если предполагается, что пользователь сможет заменить контейнер на любой PSR-совместимый, то в компонентах нельзя использовать фишки, которые есть только в Yii DI контейнере.