-
-
Notifications
You must be signed in to change notification settings - Fork 544
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
[feature] Populate all #160
Comments
Implemented in |
sweet! totally makes my day. loading i know you have your own tests, but this also works: |
One other idea, what about using an annotation for this, like @load. This way, I could just specify fields that I always wanted populated... |
Yeah, eager loading, that is also on the roadmap. Will probably do in as part of v3, as it should be pretty easy thanks to how populate support works now. |
Oh interesting, populate |
Apologies, I don't see a way to reopen this issue. |
Its |
No, it is a problem passing a boolean variable.
|
Yeah well
But I can support |
Only supporting one side of a boolean argument feels weird, but I think the JS argument is the most compelling. |
Feels weird in that I don't know of a single other API that does that. |
Fixed in dev branch. |
I'd love an option to just load a top level entity and have it fully populated without having to do anything. Maybe just
{populate: true}
.The text was updated successfully, but these errors were encountered: