For me the value would be in clearly showing that there /is/ only one
item :) If we explicitly list all options for each class then the user
can be more confident about the capabilities of each class/thing at a
glance.  Just my opinion ...

On Wed, May 08, 2013 at 04:21:30AM -0700, David Buchmann wrote:
>    In bundles/menu.rst:
> 
>  > +    The CMF MenuBundle is based on Knp Menu 1.x. The 2.0 rewrite of
>  > +    Knp Menu will add current item voters in the core Knp library.
>  > +    The CMF bundle voters are interface compatible and follow the
>  > +    same mechanism as Knp Menu to ease upgrading.
>  > +
>  > +
>  > +RequestContentIdentityVoter
>  > +~~~~~~~~~~~~~~~~~~~~~~~~~~~
>  > +
>  > +This voter looks at the ``content`` field of the menu item and compares
>  > +it with the main content attribute of the request. The name for the
>  > +request attribute is configurable, it defaults to the constant
>  > +``DynamicRouter::CONTENT_KEY``.
>  > +
>  > +You can enable this voter by setting
>  > +``symfony_cmf_menu.voters.content_identity: ~`` in your config.yml
> 
>    right, cleaned up the config thing. i don't want to do a list for just one
>    item.
> 
>    —
>    Reply to this email directly or [1]view it on GitHub.
> 
> References
> 
>    Visible links
>    1. https://github.com/symfony-cmf/symfony-cmf-docs/pull/134/files#r4132038