Closed supersmile2009 closed 2 years ago
I'm not a big fan of optional dependencies. They can bring complex problems, e.g. if you want sonata admin functionality, but not for the user bundle. The user bundle could restrict you from installing the latest bundle.
That's why I forked this project and the FOSUserBundle. If you're interested in smaller, atomic feature bundles, you can try this:
I'm not a big fan of optional dependencies. They can bring complex problems, e.g. if you want sonata admin functionality, but not for the user bundle. The user bundle could restrict you from installing the latest bundle.
The SonataAdminBundle is already an optional dependency of
So I think it's not a bad idea to do the same for the SonataUserBundle and I would say PR are welcomed.
WDYT @jordisala1991 ?
I was about to look at the same info. If that is the case for others, PRs welcome indeed.
Hi. Would making the SonataAdminBundle an optional dependency for v5 be something you could consider? It wouldn't be a BC break, since v5 is still in pre-release. And I could volunteer to implement the necessary changes. In fact running it without the Admin bundle was possible with v4 with a bit of trickery in composer.json. But service configuration in v5 makes things a bit more complicated. The key changes required to make it work are:
if
blocksonata.user.twig.global
(Sonata\UserBundle\Twig\GlobalVariables
) shouldn't have a hard dependency onSonata\AdminBundle\Admin\Pool
.Would you be open to such PR?