[TYPO3-core] RFC #15489: remove code warnings about XCLASS and naming annoyances

[Marcus Krause]

Hi!

Am 23.10.2010 09:42, schrieb Franz Holzinger:
> Le 23/10/2010 08:41, Marcus Krause a écrit :
>> Hi!
>>
>> Am 22.10.2010 17:43, schrieb Steffen Kamper:
>>> Hi,
>>>
>>> Stanislas Rolland schrieb:
>>>> Le 2010-10-22 02:31, Ernesto Baschny [cron IT] a écrit :
>>>>>
>>>>> I don't see that the EM is the right tool for that information, at
>>>>> least
>>>>> not in the table "information about the extension". Else we would
>>>>> end up
>>>>> having to include all CGL checking there. I see the "CI" server or the
>>>>> extdeveval the most appropriate place to do it.
>>>>>
>>>> Or maybe a "Developer's report" in the Report module.
>>
>> I don't think so. Problems in context of extensions should be reported
>> by EM.
> 
> No, this is very annoying if the EM reporst about missing XCLASS clauses
> and the users think they have found a severe bug. Do you really think
> that a missing XCLASS is a problem with an extension?


Please read my answer again in context of the quoted postings!!!
I wasn't writing anything about to which extent warnings or errors
regarding an extension should be reported to a TYPO3 admin.

I was only saying that moving error reporting from EM to reports module
is a bad idea.


Marcus.