View\Helper\Navigation\Menu: add flag to set page class to <li>

[Slamdunk]

In ZF1 there was the possibility to put the page class to <li> instead of internal <a>:

https://github.com/zendframework/zf1/blob/release-1.12.3/library/Zend/View/Helper/Navigation/Menu.php#L103-L108

Before:

<ul class="navigation">
    <li>
        <a class="foobar" href="site2">Site 2</a>
        <ul>
            <!-- [...] -->
        </ul>
    </li>
</ul>

After:

<ul class="navigation">
    <li class="foobar">
        <a href="site2">Site 2</a>
        <ul>
            <!-- [...] -->
        </ul>
    </li>
</ul>

This behaviour is necessary to correctly style the internal <ul> of a specific <a> page.

Tests pass, I'll rebase when global test fail will be fixed.

[vnagara]

I guess you should work around naming like: aClass (anchor), liClass(list). And functions: addAClass, addLiCalss, set[...]. Also you could put in them some default class(may take them from boostrap css).
I guess there should be done some routine work about management of css classes.

[froschdesign]

@vnagara

I guess you should work around naming like: aClass (anchor), liClass(list). And functions: addAClass, addLiCalss…

• Use the "descendant selector" in CSS and you do not need a class on both elements
• Very ugly names.

Also you could put in them some default class(may take them from boostrap css).

No default values! If you use the "Foundation" framework, the class names from "Bootstrap" are wrong.

[weierophinney]

Why the verbiage "page"? Why not simply $addClassToLi?

[weierophinney]

Also, expand "Li" to "ListItem"; abbreviations without context are often difficult to understand when just glancing through code.

[froschdesign]

@weierophinney
It is the old from version 1.12.

[froschdesign]

@weierophinney
"ListItem" 👍

[weierophinney]

Looks sane -- make the changes requested, and I'll merge for 2.2.0.

[froschdesign]

👍

[weierophinney]

Merged to develop for release with 2.2.0.