Yeah, this is something I will look into. Btw, better discuss every
thing in TBrowser PR


David Buchmann <notifications@github.com> a écrit :

>>              $routes = array();
>> -            if (null !== $admin) {
>> -                foreach ($admin->getRoutes()->getElements() as $code
>=> $route) {
>> -                    $action = explode('.', $code);
>> -                    $key = $this->mapAction(end($action));
>> -                    if (null !== $key) {
>> -                        $routes[$key] = sprintf('%s_%s',
>$admin->getBaseRouteName(), end($action));
>> -                    }
>> -                }
>> -            }
>> -            $result[$rel] = array(
>> +
>> +            // todo: sane way to register routes
>> +            $routes['edit'] = null;
>
>that is what we lose with decoupling it from sonata admin, right? do we
>need some sort of route registry that knows about route for each
>document class and sonata admins register their route with it?
>
>we could have more than one tree implementation in action, e.g. with
>different valid children rules or such.
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/sonata-project/SonataDoctrinePhpcrAdminBundle/pull/140/files#r4585964

-- 
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.