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: update dependency graphiql to v3 - autoclosed #973

Closed
wants to merge 1 commit into from
Closed

chore: update dependency graphiql to v3 - autoclosed #973

wants to merge 1 commit into from
+592 −939

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 1, 2024 •
edited
Loading

This PR contains the following updates:

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

Release Notes

graphql/graphiql (graphiql)

v3.8.3

Compare Source

Patch Changes

v3.8.2

Compare Source

Patch Changes

v3.8.1

Compare Source

Patch Changes

v3.8.0

Compare Source

Minor Changes
Patch Changes

v3.7.2

Compare Source

Patch Changes

v3.7.1

Compare Source

Patch Changes

v3.7.0

Compare Source

Minor Changes
Patch Changes

v3.6.0

Compare Source

Minor Changes
Patch Changes

v3.5.0

Compare Source

Minor Changes
Patch Changes

v3.4.1

Compare Source

Patch Changes

v3.4.0

Compare Source

Minor Changes
Patch Changes

v3.3.2

Compare Source

Patch Changes

v3.3.1

Compare Source

Patch Changes

v3.3.0

Compare Source

Minor Changes

v3.2.3

Compare Source

Patch Changes

v3.2.2

Compare Source

Patch Changes

v3.2.1

Compare Source

Patch Changes

v3.2.0

Compare Source

Minor Changes
Patch Changes

v3.1.2

Compare Source

Patch Changes

v3.1.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes

v3.0.10

Compare Source

Patch Changes

v3.0.9

Compare Source

Patch Changes

v3.0.8

Compare Source

Patch Changes

v3.0.7

Compare Source

Patch Changes

v3.0.6

Compare Source

Patch Changes

v3.0.5

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

  • Updated dependencies [2348641c]:

v3.0.4

Compare Source

Patch Changes

v3.0.3

Compare Source

Patch Changes

v3.0.2

Compare Source

Patch Changes

v3.0.1

Compare Source

Patch Changes

v3.0.0

Compare Source

Major Changes
Patch Changes

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 `defaultEdito

Configuration

📅 Schedule: Branch creation - "after 10am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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 was generated by Mend Renovate. View the repository job log.

@netlify Netlify
Copy link

netlify bot commented Jun 1, 2024 •
edited
Loading

✅ Deploy Preview for cynic-querygen-web ready!

Name Link
🔨 Latest commit 159c3b2
🔍 Latest deploy log https://app.netlify.com/sites/cynic-querygen-web/deploys/66dc7f2f9253c50008714c25
😎 Deploy Preview https://deploy-preview-973--cynic-querygen-web.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 configuration.

@renovate renovate bot force-pushed the renovate-graphiql-3.x branch from 83d5c11 to e5d963c Compare September 1, 2024 15:28
@renovate renovate bot force-pushed the renovate-graphiql-3.x branch from e5d963c to 159c3b2 Compare September 7, 2024 16:28
@renovate renovate bot changed the title chore: update dependency graphiql to v3 chore: update dependency graphiql to v3 - autoclosed Dec 22, 2024
@renovate renovate bot closed this Dec 22, 2024
@renovate renovate bot deleted the renovate-graphiql-3.x branch December 22, 2024 18:08
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.
0 participants