Skip to content
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

[Bug]: GraphQL - Using Fragment inside Inline Fragment returns only null values #868

Closed
fmaerkl-sw opened this issue Jun 25, 2024 · 1 comment · Fixed by #901
Closed

Comments

@fmaerkl-sw
Copy link

fmaerkl-sw commented Jun 25, 2024

Expected behavior

On a query using an external fragment inside an inline fragment like the following:

(...)
... on SomeType {
  ...MyFragment
}
(...)

fragment MyFragment on SomeType {
  id
  someField
}

the id is returned fine, but other fields such as someField are always null, even though a value would be available in the data.

Actual behavior

All contens of queried fields are returned.

Steps to reproduce

On https://demo.pimcore.com/pimcore-datahub-webservices/explorer/products?apikey=6332aa5e6d3d6c0be31da2a8b3442113
perform the following query:

query Car {
  getCar(id: 103) {
    ... on object_Car {
      ...CarFragment
    }
  }
}

fragment CarFragment on object_Car {
  id
  description
}

Even though the decription field contains a value, only null is returned:

{
  "data": {
    "getCar": {
      "id": "103",
      "description": null
    }
  }
}

Interestingly, all of the following queries work as expected:

query Car {
  getCar(id: 103) {
    ... on object_Car {
      id
      description
    }
  }
}
query Car {
  getCar(id: 103) {
    ...CarFragment
  }
}

fragment CarFragment on object_Car {
  id
  description
}
query Car {
  getCar(id: 103) {
    ... on object_Car {
      ...CarFragment
    }
    description2: description
  }
}

fragment CarFragment on object_Car {
  id
  description
}
@fmaerkl-sw fmaerkl-sw added the Bug label Jun 25, 2024
Copy link

Thanks a lot for reporting the issue. We did not consider the issue as "Pimcore:Priority", "Pimcore:ToDo" or "Pimcore:Backlog", so we're not going to work on that anytime soon. Please create a pull request to fix the issue if this is a bug report. We'll then review it as quickly as possible. If you're interested in contributing a feature, please contact us first here before creating a pull request. We'll then decide whether we'd accept it or not. Thanks for your understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants