We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Hi, Quite often I see the need to deserialize objects where the object is only defined by it's id.
For example:
class User {
/* @var Customer */ protected $customer;
}
here I do not want to pass customer back and forth for deserialization, but I want to be able to keep the refrence when I update the user object.
Would it be possible to have an annotation for defining that this object should be deserialized to an entity?
The text was updated successfully, but these errors were encountered:
@Type('object_reference') and then registering a custom handler for the type object_reference
@Type('object_reference')
object_reference
Sorry, something went wrong.
Ok, is it possible to create a generalized handler for this usecase?
We have the DoctrineObjectConstructor which allows you to do that.
Ok, would it be possible to get some documentation on that?
No branches or pull requests
Hi, Quite often I see the need to deserialize objects where the object is only defined by it's id.
For example:
class User {
}
here I do not want to pass customer back and forth for deserialization, but I want to be able to keep the refrence when I update the user object.
Would it be possible to have an annotation for defining that this object should be deserialized to an entity?
The text was updated successfully, but these errors were encountered: