Add support for object without JsonSerializable

[DeveloperMarius]

Hello,

I think it would be great when we add support for returning an object without the JsonSerializable.
The function get_object_vars() only returns the public variables of an object (when it is used out of the class itself). But when we create an ReflectionClass and then get the Properties, check if they are non static and add them, this would be a great alternative.
The only thing I'm not sure about is wheather to add private, protected and public variables to the return or to just return the private or the public.

~ Marius

[skipperbent]

Can't figure out if I like this. I can understand the reasoning behind it, but I'm not sure if it's something that the router should be handling (assuming what methods/data etc to return) like some kind of voodoo. Using the ReflectionClass is bad practice in my opinion as it's slow and the \JsonSerializable interface is made for exactly this.

However if this feature is really something that is needed, I think it would make more sense to create a JsonSerializable abstract class that implements the \JsonSerializable interface and then add all the parsing to that class, maybe some options to set which methods/variables to serialize etc. That way the parsing can be easily overwritten/customized if needed and the Response class will remain clean.

[DeveloperMarius]

Okay, no problem. Was just an idea :)