This repository was archived by the owner on Nov 9, 2021. It is now read-only.
[GOVCMSD8-456] update graphql module #359
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
graphql 8.x-4.0-alpha3
Release notes
This is the third alpha release of graphql module for Drupal, code name "Cold Amsterdam Winter"!
This release is mostly a security update where access handling of entities was improved in the entity-related data producers. All users are encouraged to upgrade! We also added new data producers to load entity revisions, loading taxonomy term trees and providing the currently logged-in user.
Full list of changes since 4.0-alpha2: drupal-graphql/graphql@8.x-4.0-alpha2...8.x-4...
Warning: the 4.x branch is under development and unstable. Future alpha releases can break API compatibility, so please do extensive testing when upgrading this module.
The documentation on how to use and implement graphql 4.x for your project is work in progress and can be found here: https://github.com/drupal-graphql/graphql/blob/8.x-4.x/doc/SUMMARY.md
graphql 8.x-3.0
Release notes
First stable release of GraphQL 3.x for Drupal!
Apart from a couple of bug fixes since RC 3 this release contains one breaking change. Due to security reasons the entity query support (nodeQuery, userQuery etc.) had to be marked as insecure. As result, these fields will not work out of the box for anonymous users any more. You have four options to deal with this issue:
Use persisted queries and make sure that nobody can send arbitrary filter conditions against userQuery and friends.
Implement specialized subclasses of the entity query field plugin that apply restricted filters, but don't allow to access them arbitrarily.
Replace your usage of entity query fields with views fields, since they allow you to achieve the same results.
Give anonymous users permissions to bypass field security if your environment is secure already. For example if the GraphQL endpoint is only accessible by a static site builder (Gatsby use case).
graphql 8.x-3.0-rc3
Release notes
Smaller consistency fixes and most notably basic auth support.