More options for the Nav widget (and similar ones)

[Faryshta]

I focus on the Nav widget for being the more used, other widgets that can benefit from this are Carousel, Tabs, etc.

Currently Nav::$items is an array of items, I propose to have Nav::$itemConfig which will contain a default configuration for each item or several properties like Nav::$itemOptions, Nav::$linkOptions, Nav::$labelOptions etc.

[samdark]

What's the use case for these?

[Faryshta]

For example I need all my links on the nav to contain a CSS class.

Its exactly the same use case for ActiveForm::fieldConfig property.

[samdark]

It's not really a good thing to have a class on each link. Much better to use cascade as .nav a.

[Faryshta]

@samdark i understand, thats just an example. Besides as I said ActiveForm::fieldConfig do exists for the same reason.

[samdark]

@Faryshta fieldConfig has a valid use cases. For example, I can add a closure there that adds placeholder attribute to each input.