You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I have a ConstraintViolationList instance if there some way to still be able to use a custom normalizer? The issue is that ConstraintViolationList implements \Traversable, which triggers the native php normalizer. Furthermore the class is defined by a 3rd party meaning there is no way to add annotations to it directly (or easily).
The text was updated successfully, but these errors were encountered:
I think we probably need to move the custom normalizers before the phptype
normalizer.
On Tue, Jun 7, 2011 at 12:38 AM, lsmith77 < [email protected]>wrote:
If I have a ConstraintViolationList instance if there some way to still be
able to use a custom normalizer? The issue is that ConstraintViolationList
implements \Traversable, which triggers the native php normalizer.
Furthermore the class is defined by a 3rd party meaning there is no way to
add annotations to it directly (or easily).
yeah, its kind of a pitty because in many cases it will increase the overhead, but i dont see a way around this if the end user should remain in control. that being said the end user can also place the native normalizer into the list of normalizers with a specific priority. i will send a PR
If I have a ConstraintViolationList instance if there some way to still be able to use a custom normalizer? The issue is that ConstraintViolationList implements \Traversable, which triggers the native php normalizer. Furthermore the class is defined by a 3rd party meaning there is no way to add annotations to it directly (or easily).
The text was updated successfully, but these errors were encountered: