[FLOW3-general] General Converter Behaviour
Carsten Bleicker
carsten at bleicker.de
Mon May 21 11:42:30 CEST 2012
Am i right?
If a propertyMapper returns ValidationErrors the @FLOW3\IgnoreValidation has no effects?
Am 21.05.2012 um 10:05 schrieb Carsten Bleicker:
> maybe there is also no need for exceptions.
> in the last release there was a change from default nullable to notnullable, right?
> so if the converter returns null there already an exception thrown by doctrine, right?
> so no need anymore for exceptions in converters.
>
> if column is marked as nullable anything should work as expected.
>
> carsten
>
> Am 21.05.2012 um 09:50 schrieb Carsten Bleicker:
>
>> Hi folks,
>> i want to discuss the general behaviour of converters.
>> some converters returning validation errors, but all converting anytime without returning null.
>> but in my opinion the behaviour should allways be the same.
>> first of all i would never expect validation errors in a converter. in would expect this only in validators.
>> the second idea is, to allow converters to return NULL if the property is notated with @ORM\Column(nullable=true)
>> if converters does not return null it is not possible to realize a simple start / stop date properties.
>> also no exceptions should be thrown if converter is able to return NULL.
>>
>> kind regards
>> carsten
>>
>>
>> _______________________________________________
>> FLOW3-general mailing list
>> FLOW3-general at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general
>
> _______________________________________________
> FLOW3-general mailing list
> FLOW3-general at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/flow3-general
More information about the FLOW3-general
mailing list