Skip to content

fix(deps): update graphiql monorepo #115

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 23, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphiql/plugin-explorer (source) ^0.1.15 -> ^0.3.5 age adoption passing confidence
@graphiql/react (source) ^0.17.1 -> ^0.34.1 age adoption passing confidence
@graphiql/toolkit (source) ^0.8.3 -> ^0.11.3 age adoption passing confidence
graphiql (source) ^2.4.1 -> ^2.4.7 age adoption passing confidence

Release Notes

graphql/graphiql (@​graphiql/plugin-explorer)

v0.3.5

Compare Source

Patch Changes

v0.3.4

Compare Source

Patch Changes

v0.3.3

Compare Source

Patch Changes

v0.3.2

Compare Source

Patch Changes

v0.3.1

Compare Source

Patch Changes

v0.3.0

Compare Source

Minor Changes
  • #​3330 bed5fc86 Thanks @​acao! - BREAKING CHANGE: fix lifecycle issue in plugin-explorer, change implementation pattern

    value and setValue is no longer an implementation detail, and are handled internally by plugins. the plugin signature has changed slightly as well.

    now, instead of something like this:

    import { useExplorerPlugin } from '@​graphiql/plugin-explorer';
    import { snippets } from './snippets';
    import { useExporterPlugin } from '@​graphiql/plugin-code-exporter';
    
    const App = () => {
      const [query, setQuery] = React.useState('');
      const explorerPlugin = useExplorerPlugin({
        query,
        onEdit: setQuery,
      });
      const codeExporterPlugin = useExporterPlugin({
        query,
        snippets,
      });
    
      const plugins = React.useMemo(
        () => [explorerPlugin, codeExporterPlugin],
        [explorerPlugin, codeExporterPlugin],
      );
    
      return (
        <GraphiQL
          query={query}
          onEditQuery={setQuery}
          plugins={plugins}
          fetcher={fetcher}
        />
      );
    };

    you can just do this:

    import { explorerPlugin } from '@&#8203;graphiql/plugin-explorer';
    import { snippets } from './snippets';
    import { codeExporterPlugin } from '@&#8203;graphiql/plugin-code-exporter';
    import { createGraphiQLFetcher } from '@&#8203;graphiql/toolkit';
    
    // only invoke these inside the component lifecycle
    // if there are dynamic values, and then use useMemo() (see below)
    const explorer = explorerPlugin();
    const exporter = codeExporterPlugin({ snippets });
    
    const fetcher = createGraphiQLFetcher({ url: '/graphql' });
    
    const App = () => {
      return <GraphiQL plugins={[explorer, exporter]} fetcher={fetcher} />;
    };

    or this, for more complex state-driven needs:

    import { useMemo } from 'react';
    import { explorerPlugin } from '@&#8203;graphiql/plugin-explorer';
    import { snippets } from './snippets';
    import { codeExporterPlugin } from '@&#8203;graphiql/plugin-code-exporter';
    
    const explorer = explorerPlugin();
    const fetcher = createGraphiQLFetcher({ url: '/graphql' });
    
    const App = () => {
      const { snippets } = useMyUserSuppliedState();
      const exporter = useMemo(
        () => codeExporterPlugin({ snippets }),
        [snippets],
      );
    
      return <GraphiQL plugins={[explorer, exporter]} fetcher={fetcher} />;
    };

v0.2.0

Compare Source

Minor Changes
Patch Changes
  • #​3319 2f51b1a5 Thanks @​LekoArts! - Use named Explorer import from graphiql-explorer to fix an issue where the bundler didn't correctly choose either the default or Explorer import. This change should ensure that @graphiql/plugin-explorer works correctly without graphiql-explorer being bundled.

v0.1.22

Compare Source

Patch Changes
  • #​3292 f86e4172 Thanks @​B2o5T! - fix umd build names graphiql-plugin-code-exporter.umd.js and graphiql-plugin-explorer.umd.js

v0.1.21

Compare Source

Patch Changes

v0.1.20

Compare Source

Patch Changes

v0.1.19

Compare Source

Patch Changes

v0.1.18

Compare Source

Patch Changes

v0.1.17

Compare Source

Patch Changes

v0.1.16

Compare Source

Patch Changes
graphql/graphiql (@​graphiql/react)

v0.34.1

Compare Source

Patch Changes

v0.34.0

Compare Source

Minor Changes
  • #​3946 71755b7 Thanks @​dimaMachina! - feat(@​graphiql/react): migrate React context to zustand:
    • replace useExecutionContext with useExecutionStore hook
    • replace useEditorContext with useEditorStore hook
    • replace useAutoCompleteLeafs hook with getAutoCompleteLeafs function
Patch Changes

v0.33.0

Compare Source

Minor Changes

v0.32.2

Compare Source

Patch Changes

v0.32.1

Compare Source

Patch Changes

v0.32.0

Compare Source

Minor Changes
  • #​3916 98d13a3 Thanks @​dimaMachina! - - remove the following exports from @graphiql/react and move them in @graphiql/plugin-doc-explorer package:

    • Argument
    • DefaultValue
    • DeprecationReason
    • Directive
    • DocExplorer
    • ExplorerContext
    • ExplorerContextProvider
    • ExplorerSection
    • FieldDocumentation
    • FieldLink
    • SchemaDocumentation
    • Search
    • TypeDocumentation
    • TypeLink
    • useExplorerContext
    • DOC_EXPLORER_PLUGIN
    • ExplorerContextType
    • ExplorerFieldDef
    • ExplorerNavStack
    • ExplorerNavStackItem
    • add new referencePlugin prop on PluginContextProviderProps component for plugin which is used to display the reference documentation when selecting a type.

v0.31.0

Compare Source

Minor Changes
  • #​3911 e7c436b Thanks @​dimaMachina! - - export cn from @graphiql/react

    • remove following exports from @graphiql/react and move them in @graphiql/plugin-history package:
      • History
      • HistoryContext
      • HistoryContextType
      • HistoryContextProvider
      • useHistoryContext
      • HISTORY_PLUGIN
    • remove types from @graphiql/react (use ComponentProps<typeof MyContextProviderProps> instead):
      • HistoryContextProviderProps
      • ExecutionContextProviderProps
      • EditorContextProviderProps
      • ExplorerContextProviderProps
      • PluginContextProviderProps
      • SchemaContextProviderProps
      • StorageContextProviderProps
      • GraphiQLProviderProps

v0.30.0

Compare Source

Minor Changes

v0.29.0

Compare Source

Minor Changes
Patch Changes

v0.28.2

Compare Source

Patch Changes

v0.28.1

Compare Source

Patch Changes

v0.28.0

Compare Source

Minor Changes

v0.27.1

Compare Source

Patch Changes

v0.27.0

Compare Source

Minor Changes

v0.26.2

Compare Source

Patch Changes

v0.26.1

Compare Source

Patch Changes

v0.26.0

Compare Source

Minor Changes
Patch Changes

v0.25.0

Compare Source

Minor Changes

v0.24.0

Compare Source

Minor Changes
Patch Changes

v0.23.1

Compare Source

Patch Changes

v0.23.0

Compare Source

Minor Changes
Patch Changes

v0.22.4

Compare Source

Patch Changes

v0.22.3

Compare Source

Patch Changes

v0.22.2

Compare Source

Patch Changes

v0.22.1

Compare Source

Patch Changes

v0.22.0

Compare Source

Minor Changes

v0.21.0

Compare Source

Minor Changes

v0.20.4

Compare Source

Patch Changes

v0.20.3

Compare Source

Patch Changes
  • #​3526 2b6ea316 Thanks @​benjie! - Add new useOptimisticState hook that can wrap a useState-like hook to perform optimistic caching of state changes, this helps to avoid losing characters when the user is typing rapidly. Example of usage: const [state, setState] = useOptimisticState(useOperationsEditorState());

v0.20.2

Compare Source

Patch Changes
  • #​3447 e89c432d Thanks @​acao! - Remove initialState for new hooks, add additionalComponent to toolbar to allow buttons to use context

v0.20.1

Compare Source

Patch Changes

v0.20.0

Compare Source

Minor Changes

v0.19.4

Compare Source

Patch Changes

v0.19.3

Compare Source

Patch Changes
  • #​3371 2348641c Thanks @​acao! - Solves #​2825, an old bug where new tabs were created on every refresh

    the bug occurred when:

    1. shouldPersistHeaders is not set to true
    2. headers or defaultHeaders are provided as props
    3. the user refreshes the browser

v0.19.2

Compare Source

Patch Changes

v0.19.1

Compare Source

Patch Changes

v0.19.0

Compare Source

Minor Changes
  • #​3130 9a38de29 Thanks @​lesleydreyer! - - Add a "clear history" button to clear all history as well as trash icons to clear individual history items

    • Change so item is in history items or history favorites, not both
    • Fix history label editing so if the same item is in the list more than once it edits the correct label
    • Pass the entire history item in history functions (addToHistory, editLabel, toggleFavorite, etc.) so users building their own HistoryContext.Provider will get any additional props they added to the item in their customized functions
    • Adds a "setActive" callback users can use to customize their UI when the history item is clicked

v0.18.0

Compare Source

Minor Changes
  • #​3181 9ac84bfc Thanks @​B2o5T! - remove initialTabs, use defaultTabs instead

  • #​3181 9ac84bfc Thanks @​B2o5T! - replace @reach/dialog by @radix-ui/react-dialog replace @reach/visually-hidden by @radix-ui/react-visually-hidden

  • #​3181 9ac84bfc Thanks @​B2o5T! - replace @reach/menu-button by @radix-ui/react-dropdown-menu remove @reach/listbox remove <ToolbarListbox /> and <Listbox /> components (use <Menu /> instead)

  • #​3181 9ac84bfc Thanks @​B2o5T! - fixed long list items in dropdown were hidden

    rename <Menu /> to <DropdownMenu /> rename <Menu.List /> to <DropdownMenu.Content /> rename <Menu.Item /> to <DropdownMenu.Item /> rename <Menu.Button /> to <DropdownMenu.Button />

  • #​3181 9ac84bfc Thanks @​B2o5T! - replace @reach/tooltip by @radix-ui/react-tooltip

  • #​3181 9ac84bfc Thanks @​B2o5T! - replace @reach/combobox with Combobox from @headlessui/react

  • #​3181 9ac84bfc Thanks @​B2o5T! - tabs could be reorderded

Patch Changes

v0.17.6

Compare Source

Patch Changes

v0.17.5

Compare Source

Patch Changes

v0.17.4

Compare Source

Patch Changes

v0.17.3

Compare Source

Patch Changes

v0.17.2

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

vercel bot commented Dec 23, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
docs ❌ Failed (Inspect) May 29, 2025 3:42pm

@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from 3db4d69 to 2965dcd Compare April 27, 2025 12:06
@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from 2965dcd to 99fd6f5 Compare April 30, 2025 23:51
@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from 99fd6f5 to b423b3d Compare May 3, 2025 09:46
@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from b423b3d to 368a46a Compare May 4, 2025 14:07
@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from 368a46a to 7c70371 Compare May 5, 2025 15:34
@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from 7c70371 to d3a1619 Compare May 8, 2025 03:15
@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from d3a1619 to 50d99eb Compare May 9, 2025 22:53
@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from 50d99eb to e1e8c5b Compare May 13, 2025 23:24
@renovate renovate bot force-pushed the renovate/graphiql-monorepo branch from e1e8c5b to e1bdbee Compare May 20, 2025 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants