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
{{ message }}
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.
The issue I'm having is that when I grab messages or a single message, the sentBy and receivedBy are both NULL in the rest response. The data is there and linking correctly as if I can get it lazily using regular doctrine like: $message->getSentBy()->getId()
Looking at the Hydrator strategies I can see that CollectionExtract is for displaying an embedded list of child nodes and I'm thinking CollectionLink should be for the other way around (referencing the parent), but it's always NULL.
Should I be providing somehting more than just /api/messages to get the parent's IDs or should they just be there? If I dump the response from the ObjectManager get('Entity', $id) the IDs are null, but they're treated as though they're lazy so you have to get it manually.
The text was updated successfully, but these errors were encountered:
So I have a User like so:
Who can send and receive messages, which are referencing one another using DbRef:
The issue I'm having is that when I grab messages or a single message, the sentBy and receivedBy are both NULL in the rest response. The data is there and linking correctly as if I can get it lazily using regular doctrine like:
$message->getSentBy()->getId()
Looking at the Hydrator strategies I can see that CollectionExtract is for displaying an embedded list of child nodes and I'm thinking CollectionLink should be for the other way around (referencing the parent), but it's always NULL.
My config looks like:
Should I be providing somehting more than just /api/messages to get the parent's IDs or should they just be there? If I dump the response from the ObjectManager get('Entity', $id) the IDs are null, but they're treated as though they're lazy so you have to get it manually.
The text was updated successfully, but these errors were encountered: