[email protected]

Patch Changes

• #3949 0844dc1 Thanks @dimaMachina! - prefer getComputedStyle over window.getComputedStyle

@graphiql/[email protected]

Patch Changes

• #4037 e548574 Thanks @dimaMachina! - fix execute button becomes unstyled if there are several queries present

@graphiql/[email protected]

We're thrilled to announce the release of the all-new GraphiQL 5, powered by
the latest version of the Monaco editor! 🎉

We've also added support for comments in the Variables and Headers editors.
This release is a major step forward.

The original issue for integrating the Monaco editor was opened over 3 years ago.
And the issue requesting comments support in the Variables editor was opened over 6 years ago!

See the migration guide from GraphiQL 4

@graphiql/[email protected]

We're thrilled to announce the release of the all-new GraphiQL 5, powered by
the latest version of the Monaco editor! 🎉

We've also added support for comments in the Variables and Headers editors.
This release is a major step forward.

The original issue for integrating the Monaco editor was opened over 3 years ago.
And the issue requesting comments support in the Variables editor was opened over 6 years ago!

See the migration guide from GraphiQL 4

@graphiql/[email protected]

We're thrilled to announce the release of the all-new GraphiQL 5, powered by
the latest version of the Monaco editor! 🎉

We've also added support for comments in the Variables and Headers editors.
This release is a major step forward.

The original issue for integrating the Monaco editor was opened over 3 years ago.
And the issue requesting comments support in the Variables editor was opened over 6 years ago!

See the migration guide from GraphiQL 4

@graphiql/[email protected]

We're thrilled to announce the release of the all-new GraphiQL 5, powered by
the latest version of the Monaco editor! 🎉

We've also added support for comments in the Variables and Headers editors.
This release is a major step forward.

The original issue for integrating the Monaco editor was opened over 3 years ago.
And the issue requesting comments support in the Variables editor was opened over 6 years ago!

See the migration guide from GraphiQL 4

@graphiql/[email protected]

We're thrilled to announce the release of the all-new GraphiQL 5, powered by
the latest version of the Monaco editor! 🎉

We've also added support for comments in the Variables and Headers editors.
This release is a major step forward.

The original issue for integrating the Monaco editor was opened over 3 years ago.
And the issue requesting comments support in the Variables editor was opened over 6 years ago!

See the migration guide from GraphiQL 4

[email protected]

Major Changes

• #3735 0a08642 Thanks @dimaMachina! - - Remove query, variables, headers, and response props from <GraphiQL /> and <GraphiQLProvider />
  • Add initialQuery, initialVariables and initialHeaders props
  • Fix defaultQuery, when is set will only be used for the first tab. When opening more tabs, the query editor will start out empty
  • remove useSynchronizeValue hook

Patch Changes

• Updated dependencies [0a08642]:
  • @graphiql/[email protected]

@graphiql/[email protected]

Minor Changes

• #3735 0a08642 Thanks @dimaMachina! - - Remove query, variables, headers, and response props from <GraphiQL /> and <GraphiQLProvider />
  • Add initialQuery, initialVariables and initialHeaders props
  • Fix defaultQuery, when is set will only be used for the first tab. When opening more tabs, the query editor will start out empty
  • remove useSynchronizeValue hook

[email protected]

Minor Changes

• #4025 6a50740 Thanks @dimaMachina! - set "importsNotUsedAsValues": "error" in tsconfig

• #4026 7fb5ac3 Thanks @dimaMachina! - - deprecate useExplorerContext, useHistoryContext, usePrettifyEditors, useCopyQuery, useMergeQuery, useExecutionContext, usePluginContext, useSchemaContext, useStorageContext hooks

  • fix response editor overflow on <GraphiQL.Footer />
  • export GraphiQLProps type
  • allow children: ReactNode for <GraphiQL.Toolbar />
  • change ToolbarMenu component:
    • The label and className props were removed
    • The button prop should now be a button element
  • document useGraphiQL and useGraphiQLActions hooks in @graphiql/react README.md
  • rename useThemeStore to useTheme

Patch Changes

• Updated dependencies [6a50740, 7fb5ac3]:
  • @graphiql/[email protected]
  • @graphiql/[email protected]
  • @graphiql/[email protected]