The request option "include" does not work in Parse.User.me()

[frouo]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest versions of Parse Server and the Parse JS SDK.

Issue Description

await Parse.User.me(sessionToken, { include: "books" }) does not work.

The "include" key is actually ignored, books remains unfetched.

Steps to reproduce

Create a Parse.User with a column of type Pointer array, let's call it "books", add books.

Call const me = await Parse.User.me(sessionToken, { include: "books" })

Actual Outcome

me.get("books") returns an array of unfetched Book.

Expected Outcome

Would expect that book data is available.

Environment

Server

• Parse Server version: 5.4.0
• Operating system: macOS
• Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): local

Database

• System (MongoDB or Postgres): mongodb
• Database version: 5.0.13
• Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): local

Client

• Parse JS SDK version: 3.4.4

Fix idea:

Parse-SDK-JS/src/ParseUser.js

Line 700 in ad429fc

static me(sessionToken: string, options?: RequestOptions = {}) {

  static me(sessionToken: string, options?: RequestOptions = {}) {
    const controller = CoreManager.getUserController();
    const meOptions: RequestOptions = {
      sessionToken: sessionToken,
    };
    if (options.useMasterKey) {
      meOptions.useMasterKey = options.useMasterKey;
    }
// FIX
    if (options.include) {
      meOptions.include = options.include;
    }
// end FIX
    const user = new this();
    return controller.me(user, meOptions);
  }

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

Thank you @rpfeil for confirming this issue still exists. It seems it just didn't receive much attention. Does anyone want to open a PR with a failing test case, so we can fix this?

[mtrezza]

You could open a PR, duplicate and modify one of these tests so that it executes the commands from the issue description with the me endpoint. Then we'll see whether it's replicable.

[mtrezza]

There's a guide for first time contributors, see #1657 (comment). This is all integrated, it automatically launches a Parse Server and MongoDB instance when you run the test.

[dplewis]

@rpfeil For future reference the contribution guide can be found at the bottom of the ReadMe https://github.com/parse-community/Parse-SDK-JS?tab=readme-ov-file#contributing

I'll do a PR for this issue. I realized there could be refactoring with request options as well as a potential security issue.

For a workaround try

const user = await Parse.User.me(sessionToken);
await user.fetchWithInclude(...)

Please follow the Parse Community's Code of Conduct. We understand your frustration but harassment and spam will not be tolerated in the future.

[dplewis]

Closing as this is a server issue, duplicate parse-community/parse-server#8095