Replace gourmet/knp-menu with icings/menu. #264
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
gourmet/knp-menu
doesn't seem to be maintained anymore, just like Gourmet in general.Given the current state, I'd like to propose replacing
gourmet/knp-menu
withicings/menu
, which is based on KnpMenu too, and ships with a string template renderer, and URL as well as route based matching.I've used it for internal projects for quite some time now, but had to make some larger changes for the public release, so it's currently in beta. Not sure what the rules regarding stability are, but I thought throwing the idea in the room before the first stable won't hurt.
ping @Phillaf