GraphQL Playground settings do not get set

[omgrief]

const server = new ApolloServer({
  playground: {
    settings: {
      'request.credentials': 'include',
    }
  },
  ...otherServerSettings
);

Go to your GraphQL Playground route, and notice that the settings are just default settings.

related to github.com/graphql/graphql-playground/issues/741

Adding this here as there appears to be a copy of graphql-playground-html under the @apollographql namespace, and will possibly need to be updated when they fix this.

[capaj]

I have the same issue using the latest apollo-server-express 2.1.0

[nabeelz6]

I think they might have fixed this and related setting persistence issues in prisma/graphql-playground repo:
graphql/graphql-playground#836

However, as @omgrief stated, there's a fork of playground under apollographql namespace (here?) that should pick up the new 1.8.0 release?

[javlund]

Hi - I made a PR for it here, hope someone in charge will merge it: apollographql/graphql-playground#1

[Binarytales]

I'm still having this issue. I have created a reduced test case here: https://github.com/Binarytales/jubilant-octo-telegram

I originally posted this issue against graphql-playground directly here: graphql/graphql-playground#791 (comment)

[Binarytales]

I've done a bit more digging and with the help of @HuVik I think that this issue wasn't actually fixed in graphql-playground till this PR graphql/graphql-playground#836 was released in version 1.8.0 (with 1.8.5 being that latest)

It looks like apollo-server is using 1.7.10: https://github.com/apollographql/apollo-server/blob/master/packages/apollo-server-core/src/playground.ts#L12

UPDATE: I'm still a bit confused about which versions of which packages have the needed fix and are or are not in use by various projects. However, for the benefit of future travellers stumbling across this thread I eventually discovered this post which was most illuminating: #1855 (comment)