-
Notifications
You must be signed in to change notification settings - Fork 176
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
fix(/starters/graphql-starter): add custom headers to support 4.6.0 r… #598
fix(/starters/graphql-starter): add custom headers to support 4.6.0 r… #598
Conversation
…elease of the graphql moculde
@cruno91 is attempting to deploy a commit to the Chapter Three Team on Vercel. A member of the Team first needs to authorize it. |
There are coding formatting issues in the file you modiified. You can run |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've confirmed that the GraphQL-starter fails with 4.6.0 and that this fixes the issue.
Does this also need to be rolled into |
@lukewhitmore Yep! We're going to create an 2.0.0 alpha release very soon when we get the starters fully updated to Next.js v14. #624 |
This pull request is for: (mark with an "x")
examples/*
modules/next
packages/next-drupal
starters/basic-starter
starters/graphql-starter
GitHub Issue: #588
Describe your changes
The 4.6.0 release of the GraphQL module for Drupal added checks for the headers' "Content-Type" value in requests. The existing
application/vnd.api+json
value from next-drupal'sclient.ts
fails those tests so they must be changed toapplication/json
.