[SOLVED] Graphql query using alias broken

[Eela]

I have…

• [ ] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

• [ ] Regression (a behavior that stopped working in a new release)
• [ x ] Bug report
• [ ] Performance issue
• [ ] Documentation issue or request

Current behavior

When making this kind of graphql request:

{ 
  a: findSchemaOneContent(
    id: "77777-77777-77777-7777777777"
    version: 28
  ) {
    id
    flatData {
      name
    }
  },
 b: findSchemaOneContent(
    id: "88888-88888-88888-888888-8888"
    version: 0
  ) {
    id
    flatData {
      name
    }
  },
  c: findSchemaOneContent(
    id: "99999-99999-99999-99999-99999"
    version: 1
  ) {
    id
    flatData {
      name
    }
  }
}

it will return like this:

{
  "data": {
    "a": {
      "id": "77777-77777-77777-7777777777",
      "flatData": {
        "name": "Content"
      }
    },
    "b": {
      "id": "77777-77777-77777-7777777777",
      "flatData": {
        "name": "Content"
      }
    },
    "c": {
      "id": "77777-77777-77777-7777777777",
      "flatData": {
        "name": "Content"
      }
    }
  }

Expected behavior

It should return like this:

{
  "data": {
    "a": {
      "id": "77777-77777-77777-7777777777",
      "flatData": {
        "name": "Content"
      }
    },
    "b": {
      "id": "88888-88888-88888-888888-8888",
      "flatData": {
        "name": "Content"
      }
    },
    "c": {
      "id": "99999-99999-99999-99999-99999",
      "flatData": {
        "name": "Content"
      }
    }
  }

Minimal reproduction of the problem

Environment

• [ x ] Self hosted with docker
• [ ] Self hosted with IIS
• [ ] Self hosted with other version
• [ ] Cloud version

Version: 7.8.2

Browser:

• [ x ] Chrome (desktop)
• [ ] Chrome (Android)
• [ ] Chrome (iOS)
• [ ] Firefox
• [ ] Safari (desktop)
• [ ] Safari (iOS)
• [ ] IE
• [ ] Edge

Others:

[Eela]

Also tested with latest master branch 20.10.2023 and same bug occurs there.

[Eela]

Version 7.7.0 works without issues. So the bug is on newer versions than 7.7.0.