I think we have tracked down the issue to the DelegatingValidator.
The ConstrainViolation has a propertyPath of 'children[items]
[1].data.priceImmediate'
But none of the mappings created by the DelegatingValidator match this
path...
I will create a small bundle that replicates the problem.
On May 5, 1:21 pm, Mark Fullbrook <mark.fullbr...@gmail.com> wrote:
> I have just changed the type of one of the item fields to money and
> the validation errors being thrown by
> NumberToLocalizedStringTransformer are being rendered by
> {{ form_errors( item.price ) }}. So it's the validation errors that
> are on the POPO which are being rendered at the global form level.
>
> On May 5, 12:31 pm, Mark Fullbrook <mark.fullbr...@gmail.com> wrote:
>
>
>
>
>
>
>
> > Hi Bernard,
>
> > When I call form_errors(item.myfield) on an item within a collection
> > it doesn't display the validation error message that is associated
> > with that item. Instead the error messages display at the form
> > level. So in my example snippets the validation messages for fields
> > that belong to SpotResponseItemType are only displaying when
> > form_errors(form) is called.
>
> > Great job on the Form framework btw!
> > Mark
>
> > On May 4, 9:31 pm, Bernhard Schussek <bschus...@gmail.com> wrote:
>
> > > Which errors are you talking about?
>
> > > Bernhard
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
