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.

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

fix(deps): update dependency @graphiql/plugin-explorer to v1 - abandoned #2920

Closed
wants to merge 5 commits into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 12, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphiql/plugin-explorer ^0.1.4 -> ^1.0.0 age adoption passing confidence

Release Notes

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

v1.0.0

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

v0.1.15

Compare Source

Patch Changes

v0.1.14

Compare Source

Patch Changes

v0.1.12

Compare Source

Patch Changes

v0.1.11

Compare Source

Patch Changes

v0.1.10

Compare Source

Patch Changes

v0.1.9

Compare Source

Patch Changes

v0.1.8

Compare Source

Patch Changes

v0.1.7

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 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jul 12, 2023
@changeset-bot
Copy link

changeset-bot bot commented Jul 12, 2023

🦋 Changeset detected

Latest commit: 816c557

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@graphql-yoga/graphiql Patch

Not sure what this means? Click here to learn what changesets are.

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

@renovate
Copy link
Contributor Author

renovate bot commented Jul 12, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@ardatan ardatan force-pushed the renovate/graphiql-plugin-explorer-1.x branch from 41743b7 to c99b785 Compare July 13, 2023 15:36
@github-actions
Copy link
Contributor

github-actions bot commented Jul 13, 2023

✅ Benchmark Results

     ✓ no_errors{mode:graphql}
     ✓ expected_result{mode:graphql}
     ✓ no_errors{mode:graphql-jit}
     ✓ expected_result{mode:graphql-jit}
     ✓ no_errors{mode:graphql-response-cache}
     ✓ expected_result{mode:graphql-response-cache}
     ✓ no_errors{mode:graphql-no-parse-validate-cache}
     ✓ expected_result{mode:graphql-no-parse-validate-cache}

     checks.......................................: 100.00% ✓ 195936     ✗ 0    
     data_received................................: 799 MB  6.7 MB/s
     data_sent....................................: 40 MB   330 kB/s
     http_req_blocked.............................: avg=3.04µs   min=1.6µs   med=2.4µs   max=1.04ms  p(90)=3.1µs    p(95)=3.7µs   
     http_req_connecting..........................: avg=14ns     min=0s      med=0s      max=848.9µs p(90)=0s       p(95)=0s      
     http_req_duration............................: avg=836.73µs min=379.9µs med=673.1µs max=29.43ms p(90)=1.19ms   p(95)=1.36ms  
       { expected_response:true }.................: avg=836.73µs min=379.9µs med=673.1µs max=29.43ms p(90)=1.19ms   p(95)=1.36ms  
     ✓ { mode:graphql-jit }.......................: avg=654.02µs min=379.9µs med=556.5µs max=25.59ms p(90)=737.5µs  p(95)=913.61µs
     ✓ { mode:graphql-no-parse-validate-cache }...: avg=1.29ms   min=889.5µs med=1.15ms  max=29.43ms p(90)=1.46ms   p(95)=1.93ms  
     ✓ { mode:graphql-response-cache }............: avg=723.44µs min=442µs   med=628.2µs max=14.17ms p(90)=823.99µs p(95)=987.31µs
     ✓ { mode:graphql }...........................: avg=846.24µs min=508.8µs med=727.7µs max=23.58ms p(90)=970.6µs  p(95)=1.21ms  
     http_req_failed..............................: 0.00%   ✓ 0          ✗ 97968
     http_req_receiving...........................: avg=51.35µs  min=24.6µs  med=42.5µs  max=9.36ms  p(90)=62.4µs   p(95)=82.1µs  
     http_req_sending.............................: avg=24.05µs  min=8.8µs   med=13.3µs  max=5.39ms  p(90)=26.2µs   p(95)=35µs    
     http_req_tls_handshaking.....................: avg=0s       min=0s      med=0s      max=0s      p(90)=0s       p(95)=0s      
     http_req_waiting.............................: avg=761.31µs min=339.1µs med=606.7µs max=29.31ms p(90)=1.11ms   p(95)=1.27ms  
     http_reqs....................................: 97968   816.378359/s
     iteration_duration...........................: avg=1.21ms   min=624.5µs med=1.04ms  max=29.84ms p(90)=1.59ms   p(95)=1.83ms  
     iterations...................................: 97968   816.378359/s
     vus..........................................: 1       min=1        max=1  
     vus_max......................................: 2       min=2        max=2  

@github-actions
Copy link
Contributor

github-actions bot commented Jul 13, 2023

Apollo Federation Subgraph Compatibility Results

Federation 1 SupportFederation 2 Support
_service🟢
@key (single)🟢
@key (multi)🟢
@key (composite)🟢
repeatable @key🟢
@requires🟢
@provides🟢
federated tracing🟢
@link🟢
@shareable🟢
@tag🟢
@override🟢
@inaccessible🟢
@composeDirective🟢
@interfaceObject🟢

Learn more:

@github-actions
Copy link
Contributor

github-actions bot commented Jul 13, 2023

🚀 Snapshot Release (rc)

The latest changes of this PR are available as rc on npm (based on the declared changesets):

Package Version Info
@graphql-yoga/graphiql 4.1.1-rc-20230713164201-816c5575 npm ↗︎ unpkg ↗︎

@renovate renovate bot changed the title fix(deps): update dependency @graphiql/plugin-explorer to v1 fix(deps): update dependency @graphiql/plugin-explorer to v1 - abandoned Jul 14, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Jul 14, 2023

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

@ardatan ardatan closed this Aug 4, 2023
@ardatan ardatan deleted the renovate/graphiql-plugin-explorer-1.x branch August 4, 2023 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant