Uh oh!
There was an error while loading. Please reload this page.
Use PSR container interface and deprecate our own abstraction - #21809
Conversation
rullzer
left a comment
There was a problem hiding this comment.
Maybe I'm not 100% right with the PSR... but it seems has and get have clear defined meanings...
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
8f432e7 to
988f09dCompareChristophWurst
commented
Jul 16, 2020
FYI one of my attempts was to get rid of Pimple and replace it with Symfony. But that container is not easy to use as it kind of expects to be first notified about all the known services, then compiled and finally used. But we have a more dynamic approach and allow registration later on. So I switched to the League container and that felt a lot more natural to our DI usage. However, the changes are major and we (@rullzer and I) think it would be a bad idea to cram this in so late in the 20 cycle. Thus this will be done for 21. The important part is the new PSR API. That is done with this PR. So the migration can start. |
Uh oh!
There was an error while loading. Please reload this page.
f4013f3 to
5e4f1eaCompare
Let's see if CI can find the faults. |
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
5e4f1ea to
4152216Compare
MorrisJobke
left a comment
There was a problem hiding this comment.
Fine by me 👍 Also changing to a PSR standard is the way to go
This breaks apps ability to use |
MorrisJobke
commented
Jul 28, 2020
So we need to adjust |
nickvergessen
commented
Jul 28, 2020
Yeah, fixed in #22027 |
ChristophWurst
commented
Oct 6, 2020
Documented at nextcloud/documentation#5160 |
For https://help.nextcloud.com/t/do-we-still-need-ocp-icontainer/86139
IContainerIContainerand friendsDocs are at nextcloud/documentation#2202