ACL is not fetched when I use "select"

[Samigos]

Parse Server: 2.7.4

I have an or query and I want to add some additional constraints to it, like so:

var chatRoomQuery = Parse.Query.or(currentUserAsSenderChatRoomsQuery, currentUserAsReceiverChatRoomsQuery);

chatRoomQuery.include(["sender.school"], ["receiver.school"]);
chatRoomQuery.select("lastMessage", "lastMessageWasAddedAt", "senderChatRoomName", "receiverChatRoomName", "hasSenderLeft", "hasReceiverLeft", "sender.gender", "sender.school", "receiver.gender", "receiver.school");

As you can see, I use the select constraint... I realised though, that when select is being used, ACL is not a part of the fetched object(s), even if I explicitly add it, like so:

chatRoomQuery.select("ACL", lastMessage", "lastMessageWasAddedAt", "senderChatRoomName", "receiverChatRoomName", "hasSenderLeft", "hasReceiverLeft", "sender.gender", "sender.school", "receiver.gender", "receiver.school");

Any idea why's this happening? What could I do to as a workaround?

[flovilmart]

This is a bug. Are you willing to write a failing Test and open a pull request with it? We’ll be able to fix it soon.

[Samigos]

I want to, but I have no idea how! Is there a guide or something?

[flovilmart]

@Samigos you can check our contributing guide:

https://github.com/parse-community/parse-server/blob/master/CONTRIBUTING.md

As well as all other specs in this file for example: https://github.com/parse-community/parse-server/blob/master/spec/ParseQuery.spec.js#L3002

[georgesjamous]

@i believe in Parse-Server, ACL include is enforced (as well as ObjectId, createdAt, updatedAt ..)
check : Line where key is enforced in Parse-Server

I think the problem resides in JS-SDK
here function handleSelectResult
specifically on select.forEach((field)
we are looping though the selected keys only.
Additional keys added by the server (in your case ACL) are ignored, but I don't think it should be fix here !.

I think the main issue is happening here
I am not sure why, but, for it to work otherAttributes should contain ACL but it may be filtered out by if (attr !== 'className' && attr !== '__type') {

I think, It is working for createdAt & updatedAt since the getter function in Parse.Object access the json directly.

@Samigos I just took a quick look, I am not sure that what I said is 100% correct. This could help you target the bug

I will take a stab at it in a couple of days if I have the time

[cipiripper]

You can select ACL with a dumb workaround:

query.select([ '_rperm', '_wperm']);

This is how they are stored in MongoDB, and will be passed on to it. Mongo will return _rperm (read permissions) and _wperm (write permissions) for an object, and Parse will convert them into ACL, returning it to you.

[flovilmart]

I pushed a fix, this is gonna be part of the next release of parse-server. ACL's will always be included.