Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support NormalizeableInterface #21

Closed
lsmith77 opened this issue Aug 31, 2011 · 2 comments
Closed

support NormalizeableInterface #21

lsmith77 opened this issue Aug 31, 2011 · 2 comments

Comments

@lsmith77
Copy link
Contributor

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.

@lsmith77
Copy link
Contributor Author

lsmith77 commented Sep 2, 2011

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.

For example see:
https://github.com/liip/LiipHelloBundle/blob/master/Document/Article.php#L25

@lsmith77
Copy link
Contributor Author

lsmith77 commented Sep 4, 2011

closing in favor of #23

@lsmith77 lsmith77 closed this as completed Sep 4, 2011
chasewoo pushed a commit to royuan/JMSSerializerBundle that referenced this issue Aug 7, 2013
Wrong exception message for parsing datetime
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant