[FLOW3-general] Issues with Validation and Property Mapping

[Adrian Föder]

Thanks Sebastian,

for your notes.

I now understood a bit more what happens :)

But; one thing remaining: there *is* the Validator that is able to care 
about the current locale, but as the Property Mapping kicks in first, 
the Validator may never be confrontated with a locale'd input (source) 
value.
The value that is passed to the Validator is always already a mapped 
float; this makes that Validator almost "useless" (at least its Locale 
handling capabilities).

So, I'm ending up with the question: should the property mapper also 
support Locale handling?

Very best regards,

Adrian



Am 18.04.2012 05:34, schrieb Sebastian Kurfürst:
> Hey Adrian,
>
> the process is as follows:
>
> - property mapping kicks in first, with type conversion
> - then follows validation
>
> So generally Bastian's patch is great... In your case, however, it also
> fails IIRC, because isNumeric is buggy there... No?
>
> How you could fix this for your application is writing a separate string
> to float type converter with a higher priority than the default one; and
> implement the very restrictive checking for yourself.
>
>
> Greets, Sebastian
>