laminas-mvc will be marked as security-only soon and the development we stop.
But what will happen to laminas-navigation? It relies a lot on laminas-mvc, and it can not be used with mezzio.
I would hope that it would be refactored to support Mezzio.
Only the page type Mvc and the related factories. But it is correct that the laminas-navigation does not work with Mezzio – Unfortunately, no one was interested in contributing anything either.
But you have your own library. 
The view helpers have already been removed from laminas-view:
The basic idea is to make the navigation package independent so that it can be used in any application which supports PSR-7. In addition, routers are also supported, such as those offered by Mezzio. (But there is no need for different page types for this.)
The package should also support different template engines via satellite packages. The HTML would be created by the laminas-navigation component and then there would be simple integrations in different template engines. laminas-view is one of them and then Plates, Twig, etc. – like we have in Mezzio.
Full support of web accessibility will also be added.
The access to pages would be handled by PHP‘s FilterIterator for different systems. And the navigation container is filtered before it is given to the HTML generation and template engine.
Many dependency will be removed from the main package laminas-navigation:
- laminas-config
- laminas-http
- laminas-i18n
- laminas-mvc
- laminas-permissons-acl
- laminas-router
- laminas-servicemanager
- laminas-uri
- laminas-view
Those are the plans/ideas I have so far.
1 Like
What is the plan for providing a hook into the overall filtering mechanism for allowing extension for components like ACL/RBAC that are not included to filter the container?
With access to pages I mean ACL/RBAC or something similar.
Invisible/hidden pages are also filtered out.
1 Like
Is there a proposal for the changes to Laminas Navigation as yet? If not would it be possible to contribute to it?