Bump graphiql from 1.5.19 to 2.0.3 in /dev/graphql.dev.chat.ui

[dependabot[bot]]

Bumps graphiql from 1.5.19 to 2.0.3.

Release notes

Sourced from graphiql's releases.

[email protected]

Patch Changes

• #2706 ff20a381 Thanks @​mxstbr! - Wrap the GraphiQL logo with a link to the repository

• #2715 c922719e Thanks @​thomasheyenbrock! - Add the contents of graphql and @graphiql/react as static properties to the GraphiQL component in CDN bundles so that these modules can be reused from plugin CDN bundles.

[email protected]

Patch Changes

• Updated dependencies [d65f00ea, f15ee38d, d65f00ea]:
  • @​graphiql/react@​0.11.1

[email protected]

Patch Changes

• #2699 3b642aa3 Thanks @​patrick91! - Export hooks in CDN bundle

• #2700 3acacf5b Thanks @​patrick91! - Fix cannot access initialHeaders before initialization

[email protected]

Major Changes

• #2523 fdcd9054 Thanks @​thomasheyenbrock! - BREAKING: The GraphiQL component does no longer set a property g on the window object.

• #2523 d1805200 Thanks @​thomasheyenbrock! - BREAKING: Implement a new design for the GraphiQL UI. This changes both DOM structure and class names. We consider this a breaking change as custom GraphQL IDEs built on top of GraphiQL relied on these internals, e.g. overriding styles using certain class names.

• #2523 9fc6b476 Thanks @​thomasheyenbrock! - BREAKING: The following static properties of the GraphiQL component have been removed:

  • GraphiQL.formatResult: You can use the function formatResult from @graphiql/toolkit instead.
  • GraphiQL.formatError: You can use the function formatError from @graphiql/toolkit instead.
  • GraphiQL.QueryEditor: You can use the QueryEditor component from @graphiql/react instead.
  • GraphiQL.VariableEditor: You can use the VariableEditor component from @graphiql/react instead.
  • GraphiQL.HeaderEditor: You can use the HeaderEditor component from @graphiql/react instead.
  • GraphiQL.ResultViewer: You can use the ResponseEditor component from @graphiql/react instead.
  • GraphiQL.Button: You can use the ToolbarButton component from @graphiql/react instead.
  • GraphiQL.ToolbarButton: This exposed the same component as GraphiQL.Button.
  • GraphiQL.Menu: You can use the ToolbarMenu component from @graphiql/react instead.
  • GraphiQL.MenuItem: You can use the ToolbarMenu.Item component from @graphiql/react instead.
  • GraphiQL.Group: Grouping multiple buttons side-by-side is not provided out-of-the box anymore in the new GraphiQL UI. If you want to implement a similar feature in the new vertical toolbar you can do so by adding your own styles for your custom toolbar elements. Example:

    import { GraphiQL } from 'graphiql';
    function CustomGraphiQL() {
      return (
        <GraphiQL>
          <GraphiQL.Toolbar>
            {/* Add custom styles for your buttons using the given class */}
    

... (truncated)

Changelog

Sourced from graphiql's changelog.

2.0.3

Patch Changes

• #2706 ff20a381 Thanks @​mxstbr! - Wrap the GraphiQL logo with a link to the repository

• #2715 c922719e Thanks @​thomasheyenbrock! - Add the contents of graphql and @graphiql/react as static properties to the GraphiQL component in CDN bundles so that these modules can be reused from plugin CDN bundles.

2.0.2

Patch Changes

• Updated dependencies [d65f00ea, f15ee38d, d65f00ea]:
  • @​graphiql/react@​0.11.1

2.0.1

Patch Changes

• #2699 3b642aa3 Thanks @​patrick91! - Export hooks in CDN bundle

• #2700 3acacf5b Thanks @​patrick91! - Fix cannot access initialHeaders before initialization

2.0.0

Major Changes

• #2694 e59ec32e Thanks @​acao! - BREAKING: The GraphiQL component does no longer set a property g on the window object.

• #2694 e59ec32e Thanks @​acao! - BREAKING: Implement a new design for the GraphiQL UI. This changes both DOM structure and class names. We consider this a breaking change as custom GraphQL IDEs built on top of GraphiQL relied on these internals, e.g. overriding styles using certain class names.

• #2694 e59ec32e Thanks @​acao! - BREAKING: The following static properties of the GraphiQL component have been removed:
  • GraphiQL.formatResult: You can use the function formatResult from @graphiql/toolkit instead.
  • GraphiQL.formatError: You can use the function formatError from @graphiql/toolkit instead.
  • GraphiQL.QueryEditor: You can use the QueryEditor component from @graphiql/react instead.
  • GraphiQL.VariableEditor: You can use the VariableEditor component from @graphiql/react instead.
  • GraphiQL.HeaderEditor: You can use the HeaderEditor component from @graphiql/react instead.
  • GraphiQL.ResultViewer: You can use the ResponseEditor component from @graphiql/react instead.
  • GraphiQL.Button: You can use the ToolbarButton component from @graphiql/react instead.
  • GraphiQL.ToolbarButton: This exposed the same component as GraphiQL.Button.
  • GraphiQL.Menu: You can use the ToolbarMenu component from @graphiql/react instead.
  • GraphiQL.MenuItem: You can use the ToolbarMenu.Item component from @graphiql/react instead.
  • GraphiQL.Group: Grouping multiple buttons side-by-side is not provided out-of-the box anymore in the new GraphiQL UI. If you want to implement a similar feature in the new vertical toolbar you can do so by adding your own styles for your custom toolbar elements. Example:

    import { GraphiQL } from 'graphiql';
    function CustomGraphiQL() {
      return (
        <GraphiQL>
          <GraphiQL.Toolbar>
            {/* Add custom styles for your buttons using the given class */}
    

... (truncated)

Commits

• 3e4d733 Version Packages (#2713)
• c922719 add @graphiql/plugin-explorer package (#2715)
• ff20a38 Link the GraphiQL logo to this repository (#2706)
• ddaa4bc Version Packages (#2711)
• bcd400a Version Packages (#2701)
• 3b642aa Add react hooks to CDN bundle (#2699)
• 3acacf5 Instantiate isHeadersEditorEnabled early
• a785730 Version Packages (#2696)
• e59ec32 Revert "Version Packages (#2692)" (#2694)
• 00e08db Version Packages (#2692)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)