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
still adjusting to how JMSSerialierBundle works, but I wonder if it would make sense to support the NormalizeableInterface in cases where its simply not feasible to use annotations, but where one doesnt want to register a filter (for whatever reason). also it would make it easier for people to migrate from the core Serializer to JMSSerializerBundle.
The text was updated successfully, but these errors were encountered:
as discussed on IRC at least it would be good to check of an object implements the SerializationHandlerInterface and if so call serialize() directly before attempting the registered handlers. This way it would no longer be necessary to register a handler for every special case, which should help improve performance. The same applies to deserialization of course.
still adjusting to how JMSSerialierBundle works, but I wonder if it would make sense to support the NormalizeableInterface in cases where its simply not feasible to use annotations, but where one doesnt want to register a filter (for whatever reason). also it would make it easier for people to migrate from the core Serializer to JMSSerializerBundle.
The text was updated successfully, but these errors were encountered: