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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update dependency graphiql to v2 - autoclosed #920

Closed
wants to merge 1 commit into from
Closed

chore(deps): update dependency graphiql to v2 - autoclosed #920

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 5, 2022 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphiql (source) ^1.11.5 -> ^2.4.7 age adoption passing confidence

Release Notes

graphql/graphiql

v2.4.7

Compare Source

Patch Changes

v2.4.6

Compare Source

Patch Changes

v2.4.5

Compare Source

Patch Changes

v2.4.4

Compare Source

Patch Changes

v2.4.3

Compare Source

Patch Changes

v2.4.2

Compare Source

Patch Changes

v2.4.1

Compare Source

Patch Changes

v2.4.0

Compare Source

Minor Changes
  • #​3012 65f5176a Thanks @​benjie! - GraphiQL now maintains the DocExplorer navigation stack as best it can when the schema is updated
Patch Changes

v2.3.0

Compare Source

Minor Changes
Patch Changes

v2.2.0

Compare Source

Minor Changes
Patch Changes

v2.1.0

Compare Source

Minor Changes
Patch Changes

v2.0.13

Compare Source

Patch Changes

v2.0.12

Compare Source

Patch Changes

v2.0.11

Compare Source

Patch Changes

v2.0.10

Compare Source

Patch Changes

v2.0.9

Compare Source

Patch Changes

v2.0.8

Compare Source

Patch Changes

v2.0.7

Compare Source

Patch Changes

v2.0.6

Compare Source

Patch Changes

v2.0.5

Compare Source

Patch Changes

v2.0.4

Compare Source

Patch Changes

v2.0.3

Compare Source

Patch Changes
  • #​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.

v2.0.2

Compare Source

Patch Changes

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

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 */}
        <div className="button-group">
          <button>1</button>
          <button>2</button>
          <button>3</button>
        </div>
      </GraphiQL.Toolbar>
    </GraphiQL>
  );
}
  • #​2694 e59ec32e Thanks @​acao! - BREAKING: The following exports of the graphiql package have been removed:
    • DocExplorer: Now exported from @graphiql/react as DocExplorer
      • The schema prop has been removed, the component now uses the schema provided by the ExplorerContext
    • fillLeafs: Now exported from @graphiql/toolkit as fillLeafs
    • getSelectedOperationName: Now exported from @graphiql/toolkit as getSelectedOperationName
    • mergeAst: Now exported from @graphiql/toolkit as mergeAst
    • onHasCompletion: Now exported from @graphiql/react as onHasCompletion
    • QueryEditor: Now exported from @graphiql/react as QueryEditor
    • ToolbarMenu: Now exported from @graphiql/react as ToolbarMenu
    • ToolbarMenuItem: Now exported from @graphiql/react as ToolbarMenu.Item
    • ToolbarSelect: Now exported from @graphiql/react as ToolbarListbox
    • ToolbarSelectOption: Now exported from @graphiql/react as ToolbarListbox.Option
    • VariableEditor: Now exported from @graphiql/react as VariableEditor
    • type Fetcher: Now exported from @graphiql/toolkit
    • type FetcherOpts: Now exported from @graphiql/toolkit
    • type FetcherParams: Now exported from @graphiql/toolkit
    • type FetcherResult: Now exported from @graphiql/toolkit
    • type FetcherReturnType: Now exported from @graphiql/toolkit
    • type Observable: Now exported from @graphiql/toolkit
    • type Storage: Now exported from @graphiql/toolkit
    • type SyncFetcherResult: Now exported from @graphiql/toolkit
  • #​2694 e59ec32e Thanks @​acao! - BREAKING: The GraphiQL component has been refactored to be a function component. Attaching a ref to this component will no longer provide access to props, state or class methods. In order to interact with or change GraphiQL state you need to use the contexts and hooks provided by the @graphiql/react package. More details and examples can be found in the migration guide.
  • #​2694 e59ec32e Thanks @​acao! - BREAKING: The following props of the GraphiQL component have been changed:
    • The props defaultVariableEditorOpen and defaultSecondaryEditorOpen have been merged into one prop defaultEditorToolsVisibility. The default behavior if this prop is not passed is that the editor tools are shown if at least one of the secondary editors has contents. You can pass the following values to the prop:
      • Passing false hides the editor tools.
      • Passing true shows the editor tools.
      • Passing "variables" explicitly shows the variables editor.
      • Passing "headers" explicitly shows the headers editor.
    • The props docExplorerOpen, onToggleDocs and onToggleHistory have been removed. They are replaced by the more generic props visiblePlugin (for controlling which plugin is visible) and onTogglePluginVisibility (which is called each time the visibility of any plugin changes).
    • The headerEditorEnabled prop has been renamed to isHeadersEditorEnabled.
    • The ResultsTooltip prop has been renamed to responseTooltip.
    • Tabs are now always enabled. The tabs prop has therefore been replaced with a prop onTabChange. If you used the tabs prop before to pass this function you can change your implementation like so: 
      <GraphiQL
-  tabs={{ onTabChange: (tabState) => {/* do something */} }}
+  onTabChange={(tabState) => {/* do something */}}
/>
Minor Changes
  • #​2694 e59ec32e Thanks @​acao! - GraphiQL now ships with a dark theme. By default the interface respects the system settings, the theme can also be explicitly chosen via the new settings dialog.
Patch Changes

Configuration

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

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Mend Renovate. View repository job log here.

@changeset-bot
Copy link

changeset-bot bot commented Sep 5, 2022 •
edited
Loading

⚠️ No Changeset found

Latest commit: cf7797e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Sep 5, 2022 •
edited
Loading

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

Name Status Preview Comments Updated (UTC)
graphql-ez ❌ Failed (Inspect) May 28, 2023 0:11am

@renovate renovate bot force-pushed the renovate/graphiql-2.x branch from 841a803 to e7ffef2 Compare May 1, 2023 15:56
@renovate renovate bot force-pushed the renovate/graphiql-2.x branch from e7ffef2 to 0863bd7 Compare May 3, 2023 10:44
@renovate renovate bot force-pushed the renovate/graphiql-2.x branch from 0863bd7 to 5351a7a Compare May 8, 2023 13:35
@renovate renovate bot changed the title chore(deps): update dependency graphiql to v2 chore(deps): update dependency graphiql to v2 - autoclosed Jun 24, 2023
@renovate renovate bot closed this Jun 24, 2023
@renovate renovate bot deleted the renovate/graphiql-2.x branch June 24, 2023 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
0 participants