Do you see such Twig Extensions interesting for Symfony/UX?

[alexander-schranz]

I created a whole Extranet like library for a client based on some symfony ux and a lot of stimulus / turbo stuff. In this library we have three I think very usefull Twig extension which might be nice for symfony UX itself.

Navigation Twig Extension

The navigation twig extension uses Route Options to create a Navigation. Based on navigationContext and navigationContextSection options.

{% set navigationItems = get_static_navigation('main') %}

Tab Twig Extension

If the current route has a tabGroup all items with the same tabGroup are returned here.

{% set tabItems = get_static_tabs() %}

Breadcrumb Twig Extension

If the current route has a breadcrumbParent all parents item are returned here.

{% set breadcrumbItems = get_static_breadcrumb() %}

---

Example of our route definitions. As it are options you could also use attributes, php or xml route definitions.

extranet_dashboard:
    path: /extranet
    controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
    defaults:
        template: '@Extranet/base.html.twig'
    options:
        title: app.extranet.dashboard
        icon: 'outline/home'
        navigationContext: 'main'
        navigationContextSection: 'top'

extranet_other:
    path: /extranet/other
    controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
    defaults:
        template: '@Extranet/base.html.twig'
    options:
        title: app.extranet.other
        icon: 'outline/document-report'
        navigationContext: 'main'
        navigationContextSection: 'models'
        breadcrumbParent: 'extranet_dashboard'

extranet_other_more:
    path: /extranet/other/{id}
    controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
    defaults:
        template: '@Extranet/base.html.twig'
    options:
        title: app.extranet.other_more
        breadcrumbParent: 'extranet_other'
        icon: 'outline/user'
        tabGroup: 'group'

extranet_other_more_detail:
    path: /extranet/other/{id}/detail
    controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
    defaults:
        template: '@Extranet/base.html.twig'
    options:
        title: app.extranet.other_more_detail
        breadcrumbParent: 'extranet_other_more'
        icon: 'outline/qrcode'
        tabGroup: 'group'

extranet_other_more_detail_subview:
    path: /extranet/other/{id}/detail/subview
    controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
    defaults:
        template: '@Extranet/base.html.twig'
    options:
        title: app.extranet.other_more_detail
        breadcrumbParent: 'extranet_other_more_detail'

extranet_tab_redirect:
    path: /extranet/other/{id}/sub
    controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
    defaults:
        template: '@Extranet/base.html.twig'
    options:
        title: app.extranet.tab_redirect
        breadcrumbParent: 'extranet_other_more'
        icon: 'outline/qrcode'
        tabGroup: 'group'

extranet_tab_sub:
    path: /extranet/other/{id}/sub/tab
    controller: Symfony\Bundle\FrameworkBundle\Controller\TemplateController
    defaults:
        template: '@Extranet/base.html.twig'
    options:
        title: app.extranet.sub_tab
        icon: 'outline/qrcode'
        breadcrumbParent: 'extranet_tab_redirect'
        tabParent: 'extranet_tab_redirect'

We are using .yaml as it is easier to control the order of the items instead of have a additional priority but that could be added.:

[Kocal]

Thanks for considering us!

I don't think such a library embraces the Symfony UX philosophy, here it's purely backend and nothing about frontend, right? Or am I missing something?

[alexander-schranz]

Yes no UI. Just twig extension data / route provider. More interesting for Toolkit which could generate Navigation using the extension to load real routes.

[stof]

This looks a bit like what KnpMenuBundle does, but with a different API to configure. KnpMenuBundle does not use route options as the way to configure this, as that's not easy to access in a performant way (route options are not exposed in cached APIs of the router) and less flexible (what if multiple navigation contexts should include links to the same route ?)

[alexander-schranz]

@stof we support ['main', 'footer'].

The KnpMenuBundle looks for me focused on rendering things. Not just providing the routes.

route options are not exposed in cached APIs of the router

Adding a cache for the data required from the $this->router->getRouteCollection() is I think easy. Can even be a system cache which we warm up at cache:clear as the routes are hardcoded.

[smnandre]

symfony ux and a lot of stimulus / turbo stuff.

Feel free to share if you have other stuff too :)