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

chore(deps): update graphqlcodegenerator monorepo (major) #1833

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 21, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@graphql-cli/codegen (source) 1.17.27 -> 3.0.4 age adoption passing confidence
@graphql-codegen/add (source) 2.0.2 -> 5.0.2 age adoption passing confidence
@graphql-codegen/typescript (source) 1.23.0 -> 4.0.7 age adoption passing confidence
@graphql-codegen/typescript-operations (source) 1.18.4 -> 4.2.1 age adoption passing confidence
@graphql-codegen/typescript-react-apollo (source) 2.3.1 -> 4.3.0 age adoption passing confidence
@graphql-codegen/typescript-resolvers (source) 1.20.0 -> 4.1.0 age adoption passing confidence

Release Notes

dotansimha/graphql-code-generator (@​graphql-cli/codegen)

v3.0.4

Compare Source

v3.0.3

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source

v2.4.25

Compare Source

v2.4.24

Compare Source

v2.4.23

Compare Source

v2.4.22

Compare Source

v2.4.21

Compare Source

v2.4.20

Compare Source

v2.4.18

Compare Source

v2.4.17

Compare Source

v2.4.16

Compare Source

v2.4.15

Compare Source

v2.4.14

Compare Source

v2.4.13

Compare Source

v2.4.12

Compare Source

v2.4.11

Compare Source

v2.4.10

Compare Source

v2.4.9

Compare Source

v2.4.8

Compare Source

v2.4.7

Compare Source

v2.4.6

Compare Source

v2.4.5

Compare Source

v2.4.4

Compare Source

v2.4.3

Compare Source

v2.4.2

Compare Source

v2.4.1

Compare Source

v2.4.0

Compare Source

v2.3.13

Compare Source

v2.3.12

Compare Source

v2.3.11

Compare Source

v2.3.10

Compare Source

v2.3.9

Compare Source

v2.3.8

Compare Source

Patch Changes

v2.3.7

Compare Source

Patch Changes

v2.3.6

Compare Source

Patch Changes

v2.3.5

Compare Source

Patch Changes

v2.3.4

Compare Source

Patch Changes

v2.3.3

Compare Source

Patch Changes

v2.3.2

Compare Source

Patch Changes

v2.3.1

Compare Source

Patch Changes

v2.3.0

Compare Source

Minor Changes
Patch Changes

v2.2.6

Compare Source

Patch Changes

v2.2.5

Compare Source

Patch Changes

v2.2.4

Compare Source

Patch Changes

v2.2.3

Compare Source

Patch Changes

v2.2.2

Compare Source

Patch Changes

v2.2.1

Compare Source

Patch Changes

v2.2.0

Compare Source

Minor Changes
  • 754a337: Performance Profiler --profile
Patch Changes

v2.1.7

Compare Source

Patch Changes

v2.1.6

Compare Source

Patch Changes

v2.1.5

Compare Source

Patch Changes

v2.1.4

Compare Source

Patch Changes

v2.1.3

Compare Source

Patch Changes

v2.1.2

Compare Source

Patch Changes

v2.1.1

Compare Source

Patch Changes

v2.1.0

Compare Source

Minor Changes
Patch Changes

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

Major Changes
  • b0cb13d: Update to latest graphql-tools and graphql-config version.

    ‼️ ‼️ ‼️ Please note ‼️ ‼️ ‼️:

    This is a breaking change since Node 10 is no longer supported in graphql-tools, and also no longer supported for Codegen packages.

Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/add)

v5.0.2

Compare Source

Patch Changes

v5.0.1

Compare Source

Patch Changes

v5.0.0

Compare Source

Major Changes
Patch Changes

v4.0.1

Compare Source

Patch Changes

v4.0.0

Compare Source

Major Changes
Patch 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.1

Compare Source

Patch Changes

v3.1.0

Compare Source

Minor Changes
Patch Changes

v3.0.0

Compare Source

Major Changes
  • b0cb13d: Update to latest graphql-tools and graphql-config version.

    ‼️ ‼️ ‼️ Please note ‼️ ‼️ ‼️:

    This is a breaking change since Node 10 is no longer supported in graphql-tools, and also no longer supported for Codegen packages.

Patch Changes
dotansimha/graphql-code-generator (@​graphql-codegen/typescript)

v4.0.7

Compare Source

Patch Changes

v4.0.6

Compare Source

Patch Changes

v4.0.5

Compare Source

Patch Changes

v4.0.4

Compare Source

Patch Changes

v4.0.3

Compare Source

Patch Changes

v4.0.2

Compare Source

Patch Changes

v4.0.1

Compare Source

Patch Changes
  • #​9497 2276708d0 Thanks @​eddeee888! - Revert default ID scalar input type to string

    We changed the ID Scalar input type from string to string | number in the latest major version of typescript plugin. This causes issues for server plugins (e.g. typescript-resolvers) that depends on typescript plugin. This is because the scalar type needs to be manually inverted on setup which is confusing.

  • Updated dependencies [2276708d0]:

v4.0.0

Compare Source

Major Changes
  • #​9375 ba84a3a27 Thanks @​eddeee888! - Implement Scalars with input/output types

    In GraphQL, Scalar types can be different for client and server. For example, given the native GraphQL ID:

    • A client may send string or number in the input
    • A client receives string in its selection set (i.e output)
    • A server receives string in the resolver (GraphQL parses string or number received from the client to string)
    • A server may return string or number (GraphQL serializes the value to string before sending it to the client )

    Currently, we represent every Scalar with only one type. This is what codegen generates as base type:

    export type Scalars = {
      ID: string;
    };

    Then, this is used in both input and output type e.g.

    export type Book = {
      __typename?: 'Book';
      id: Scalars['ID']; // Output's ID can be `string` 👍
    };
    
    export type QueryBookArgs = {
      id: Scalars['ID']; // Input's ID can be `string` or `number`. However, the type is only `string` here 👎
    };

    This PR extends each Scalar to have input and output:

    export type Scalars = {
      ID: {
        input: string | number;
        output: string;
      };
    };

    Then, each input/output GraphQL type can correctly refer to the correct input/output scalar type:

    export type Book = {
      __typename?: 'Book';
      id: Scalars['ID']['output']; // Output's ID can be `string` 👍
    };
    
    export type QueryBookArgs = {
      id: Scalars['ID']['input']; // Input's ID can be `string` or `number` 👍
    };

    Note that for typescript-resolvers, the type of ID needs to be inverted. However, the referenced types in GraphQL input/output types should still work correctly:

    export type Scalars = {
      ID: {
        input: string;
        output: string | number;
      }
    }
    
    export type Book = {
      __typename?: "Book";
      id: Scalars["ID"]['output']; // Resolvers can return `string` or `number` in ID fields 👍
    };
    
    export type QueryBookArgs = {
      id: Scalars["ID"]['input']; // Resolvers receive `string` in ID fields 👍
    };
    
    export type ResolversTypes = {
      ID: ID: ResolverTypeWrapper<Scalars['ID']['output']>; // Resolvers can return `string` or `number` in ID fields 👍
    }
    
    export type ResolversParentTypes = {
      ID: Scalars['ID']['output']; // Resolvers receive `string` or `number` from parents 👍
    };

    Config changes:

    1. Scalars option can now take input/output types:
    config: {
      scalars: {
        ID: {
          input: 'string',
          output: 'string | number'
        }
      }
    }
    1. If a string is given (instead of an object with input/output fields), it will be used as both input and output types:
    config: {
      scalars: {
        ID: 'string'; // This means `string` will be used for both ID's input and output types
      }
    }
    1. BREAKING CHANGE: External module Scalar types need to be an object with input/output fields
    config: {
      scalars: {
        ID: './path/to/scalar-module';
      }
    }

    If correctly, wired up, the following will be generated:

    // Previously, imported `ID` type can be a primitive type, now it must be an object with input/output fields
    import { ID } from './path/to/scalar-module';
    
    export type Scalars = {
      ID: { input: ID['input']; output: ID['output'] };
    };

    BREAKING CHANGE: This changes Scalar types which could be referenced in other plugins. If you are a plugin maintainer and reference Scalar, please update your plugin to use the correct input/output types.

  • bb66c2a31 Thanks @​n1ru4l! - Require Node.js >= 16. Drop support for Node.js 14

Minor Changes
  • #​9196 3848a2b73 Thanks @​beerose! - Add @defer directive support

    When a query includes a deferred fragment field, the server will return a partial response with the non-deferred fields first, followed by the remaining fields once they have been resolved.

    Once start using the @defer directive in your queries, the generated code will automatically include support for the directive.

    // src/index.tsx
    import { graphql } from './gql';
    const OrdersFragment = graphql(`
      fragment OrdersFragment on User {
        orders {
          id
          total
        }
      }
    `);
    const GetUserQuery = graphql(`
      query GetUser($id: ID!) {
        user(id: $id) {
          id
          name
          ...OrdersFragment @&#8203;defer
        }
      }
    `);

    The generated type for GetUserQuery will have information that the fragment is incremental, meaning it may not be available right away.

    // gql/graphql.ts
    export type GetUserQuery = { __typename?: 'Query'; id: string; name: string } & ({
      __typename?: 'Query';
    } & {
      ' $fragmentRefs'?: { OrdersFragment: Incremental<OrdersFragment> };
    });

    Apart from generating code that includes support for the @defer directive, the Codegen also exports a utility function called isFragmentReady. You can use it to conditionally render components based on whether the data for a deferred
    fragment is available:

    const OrdersList = (props: { data: FragmentType<typeof OrdersFragment> }) => {
      const data = useFragment(OrdersFragment, props.data);
      return (
        // render orders list
      )
    };
    
    function App() {
      const { data } = useQuery(GetUserQuery);
      return (
        {data && (
          <>
            {isFragmentReady(GetUserQuery, OrdersFragment, data)
    					&& <OrdersList data={data} />}
          </>
        )}
      );
    }
    export default App;
  • #​9304 e1dc75f3c Thanks @​esfomeado! - Added support for disabling suffixes on Enums.

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.

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

@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from aa219a1 to bf1a03f Compare August 25, 2021 19:48
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 7116a2d to a75cd85 Compare September 7, 2021 11:04
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from a839953 to 709ad56 Compare September 10, 2021 17:40
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 028d5b3 to 214eee2 Compare October 3, 2021 13:35
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 8d1e25d to fe36389 Compare October 14, 2021 14:01
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 84a9564 to f0c63fa Compare November 5, 2021 14:49
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from f3980d9 to b96133d Compare November 18, 2021 10:43
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from b96133d to 59c21d3 Compare December 30, 2021 09:20
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 59c21d3 to b0f47f6 Compare January 13, 2022 11:42
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from b0f47f6 to 3c37971 Compare March 7, 2022 11:55
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 3c37971 to 059c40d Compare March 26, 2022 13:31
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 059c40d to f550f58 Compare May 16, 2022 03:04
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 2eac0af to f4bbc6c Compare June 10, 2022 18:28
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 90e2d1e to 27a68f5 Compare July 4, 2022 12:17
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 244585d to 6ca8109 Compare July 13, 2022 17:56
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 6ca8109 to 43a3506 Compare July 19, 2022 16:16
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 43a3506 to 3f74171 Compare July 20, 2022 17:03
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 3f74171 to 740a6b8 Compare September 25, 2022 16:50
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 740a6b8 to 086a97b Compare November 20, 2022 09:32
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 086a97b to 78f174f Compare March 16, 2023 21:53
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 78f174f to 0de080f Compare April 17, 2023 12:58
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 0de080f to ead1fb9 Compare May 28, 2023 09:30
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from ead1fb9 to 36f274f Compare June 19, 2023 10:32
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 36f274f to 28b49c9 Compare September 25, 2023 22:29
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from 28b49c9 to 693e7d1 Compare October 25, 2023 01:45
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 3 times, most recently from 89d0e26 to 2f6d3c9 Compare February 8, 2024 19:05
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch 2 times, most recently from 6156246 to b4a0f6e Compare February 22, 2024 21:59
@renovate renovate bot force-pushed the renovate/major-graphqlcodegenerator-monorepo branch from b4a0f6e to fdba996 Compare May 17, 2024 14:05
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.

None yet

0 participants