search

zikula / core

Zikula Core Framework
GNU Lesser General Public License v3.0
238 stars 66 forks source link

Decide about capabilities #3620

Closed Guite closed 4 years ago

Guite commented 7 years ago

We need to decide whether capabilities are still needed or completely replaced by tagged services (actually many capabilities were already replaced and only remain for BC). In the latter case the capability api should be deprecated in 1.5 and removed in 2.0.

craigh commented 7 years ago

I think most of the capability keys are handled via DI tags now with the exception of user and admin route identifiers. Not sure about this though.

craigh commented 7 years ago

also yet sure about \Zikula\ExtensionsModule\Api\ApiInterface\CapabilityApiInterface::CATEGORIZABLE

Guite commented 7 years ago

As the others are already deprecated we could also postpone this to 2.1.0.

Guite commented 7 years ago

@sstok suggests https://github.com/rollerworks/RouteAutowiringBundle for auto-wiring user and admin routes. Postponing to 2.1.0.

Guite commented 4 years ago

Moving to 3.0.0 again. @craigh something we should talk about in Slack.

Guite commented 4 years ago

Closing as we still need capabilities as well as CapabilityApi.