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

🐛 Align apollo-server config with state of embeds #7432

Conversation

mayakoneval
Copy link
Contributor

@mayakoneval mayakoneval commented Mar 9, 2023

We added hideCookieToggle and initialState.includeCookies in the embedded Sandbox config. We then accidentally added hideCookieToggle to the embedded Explorer, and we should have only added it to the embedded Sandbox in this repo.

This PR

  1. puts includeCookies back in the embedded Explorer
  2. removes hideCookieToggle in the embedded Explorer
  3. don't spread the entire config into the explorer config, name the arguments
  4. remove redundant ?? undefineds
Bug fix: tldr revert a previous change that stops passing includeCookies from the prod landing page config.

Who was affected? 

Any Apollo Server instance that passes a `graphRef` to a production landing page with a non-default `includeCookies` value that does not match the `Include cookies` setting on your registered variant on studio.apollographql.com.

How were they affected?

From release 4.4.0 to this patch release, folks affected would have seen their Explorer requests being sent with cookies included only if they had set `Include cookies` on their variant. Cookies would not havhe been included by default.

… landing page / Explorer, which is deprecated but necessary for backwards compatibility
@netlify
Copy link

netlify bot commented Mar 9, 2023

Deploy Preview for apollo-server-docs ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit 46872c1
🔍 Latest deploy log https://app.netlify.com/sites/apollo-server-docs/deploys/64097b56346464000825ba52
😎 Deploy Preview https://deploy-preview-7432--apollo-server-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@codesandbox-ci
Copy link

codesandbox-ci bot commented Mar 9, 2023

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@trevor-scheer trevor-scheer merged commit 8cbc614 into apollographql:main Mar 9, 2023
@github-actions github-actions bot mentioned this pull request Mar 9, 2023
trevor-scheer pushed a commit that referenced this pull request Mar 10, 2023
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @apollo/server@4.5.0

### Minor Changes

- [#7431](#7431)
[`7cc163ac8`](7cc163a)
Thanks [@mayakoneval](https://github.com/mayakoneval)! - In the Apollo
Server Landing Page Local config, you can now automatically turn off
autopolling on your endpoints as well as pass headers used to introspect
your schema, embed an operation from a collection, and configure whether
the endpoint input box is editable. In the Apollo Server Landing Page
Prod config, you can embed an operation from a collection & we fixed a
bug introduced in release 4.4.0

    Example of all new config options:

    ```
    const server = new ApolloServer({
      typeDefs,
      resolvers,
      plugins: [
        process.env.NODE_ENV === 'production'
          ? ApolloServerPluginLandingPageProductionDefault({
              graphRef: 'my-graph-id@my-graph-variant',
              collectionId: 'abcdef',
              operationId: '12345'
              embed: true,
              footer: false,
            })
          : ApolloServerPluginLandingPageLocalDefault({
              collectionId: 'abcdef',
              operationId: '12345'
              embed: {
                initialState: {
                  pollForSchemaUpdates: false,
                  sharedHeaders: {
"HeaderNeededForIntrospection": "ValueForIntrospection"
                  },
                },
                endpointIsEditable: true,
              },
              footer: false,
            }),
      ],
    });

    ```

- [#7430](#7430)
[`b694bb1dd`](b694bb1)
Thanks [@mayakoneval](https://github.com/mayakoneval)! - We now send
your @apollo/server version to the embedded Explorer & Sandbox used in
the landing pages for analytics.

### Patch Changes

- [#7432](#7432)
[`8cbc61406`](8cbc614)
Thanks [@mayakoneval](https://github.com/mayakoneval)! - Bug fix: TL;DR
revert a previous change that stops passing includeCookies from the prod
landing page config.

    Who was affected?

Any Apollo Server instance that passes a `graphRef` to a production
landing page with a non-default `includeCookies` value that does not
match the `Include cookies` setting on your registered variant on
studio.apollographql.com.

    How were they affected?

From release 4.4.0 to this patch release, folks affected would have seen
their Explorer requests being sent with cookies included only if they
had set `Include cookies` on their variant. Cookies would not have been
included by default.

## @apollo/server-integration-testsuite@4.5.0

### Patch Changes

- Updated dependencies
\[[`7cc163ac8`](7cc163a),
[`8cbc61406`](8cbc614),
[`b694bb1dd`](b694bb1)]:
    -   @apollo/server@4.5.0

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants