-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
query.include() does not include the relation objects #4138
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
Comments
@srameshr If that property is a Relation, yes, it won't include the results. You need to do |
You can read more here: |
@natanrolnik How do I select few fields from the
The response does not include any fields from |
I'm pretty sure that |
It (nesting) used to work previously with In detail:
Now when I query for |
If nested select used to work, there’s a regression; but I highly doubt we’d introduce such regression without breaking a few tests. |
@flovilmart I agree. Or was it some bug on my end? Im not sure! Any answer to the detail part in my previous comment? |
actually, it seems heavily covered already... https://github.com/parse-community/parse-server/blob/master/spec/ParseQuery.spec.js#L2844 What version of the server are you running? Can you provide verbose logs when running this query? |
This selection is not working for me. I will update with the logs. |
Yeah, and it’s properly teSted and covered on each release. |
|
looks like it's working as expected to me.
the default keys |
Doesn't this supposedly bring the liked posts from the current user?
I keep getting this result: |
Issue Description
query.include() does not include the relation objects
Steps to reproduce
Test
has a relation to User class on columnuserRel
."userRel":{"__type":"Relation","className":"_User"}
.Expected Results
The whole user object should be sent in response.
Actual Outcome
The response just includes
"userRel":{"__type":"Relation","className":"_User"}
even though 5 users are in this relation.Environment Setup
Server
"parse": "^1.10.0", "parse-server":"^2.5.3"
Database
Logs/Trace
Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment.
The text was updated successfully, but these errors were encountered: