Comment length check should be increased or check for classnames

[evoWeb]

Problem is, that explicit classnames result easily in lengthy function comments like for example

    /**
     * Initialize file transfer
     *
     * @throws Tx_MfcDatabaseSynchronization_Exception_NotBothFileSystemsMayBeLocal
     * @throws Tx_MfcDatabaseSynchronization_Exception_NotEnoughFileSystemsConfigured
     * @throws Tx_MfcDatabaseSynchronization_Exception_BothFileSystemsNeedToBeInstantiated
     * @return void
     */

With 6.2 and namespaces this can be easily more. Thats why the check for comments in general is ok but in @throws, @param and @return is more then annoying.

[Konafets]

This implies a change of the CGL. Please open a ticket at http://forge.typo3.org/projects/typo3cms-doc-coding-guidelines/issues/new

[evoWeb]

Issue created

Edit:
https://forge.typo3.org/issues/59630

[Lefaux]

is this relevant? With Namespaces the length should get shorter, not longer (hint: use imports).

[evoWeb]

As 'use' is not coerced and still a valid usage the length could still be an issue thus its still relevant.

http://docs.typo3.org/typo3cms/CodingGuidelinesReference/singlehtml/ states only

'use statements can be added to this section.'

So as long as fullyqualified namespaces are a valid usage, i would ask to reflected it in the codesniffer.