[TYPO3-dev] Deprecation strategy for BE viewhelpers

[Steffen Müller]

Hi.

On 05.08.2013 10:07 Christian Kuhn wrote:
> You create a dependency to a foreign extension just because of a single
> view helper this way. This is tight coupling for no good reason, we
> shouldn't do this: The view helpers in extension manager, belog, beuser
> and so on are dedicated to this extension only and can be changed at will.
> 

This is hard to understand for those who have not deep insight to the
core structure:
We have sysext:core, which contains the core API, then we have
sysext:extensionmanager which is part of the core, but VH are non-API,
then we have sysext:fluid which VH are API.
IMHO chances are high to misunderstand this concept and rely on VH from
extensionmanager, because they have public keypwrd and are shipped with
the core. To keep our developers happy, we'd better deprecate UNTIL we
have @internal notation.

> We should imho state somewhere: "Only view helpers in ext:fluid are
> public API and are part of the usual deprecation strategy, view helpers
> in other core extensions are not public API and can change without
> further notice." Maybe we can also annotate the other extensions view
> helpers with @internal to make this clear when reading the code.

+1


-- 
cheers,
Steffen

Active Contributor TYPO3 CMS

TYPO3 Blog: http://www.t3node.com/
Twitter: @t3node - http://twitter.com/t3node