[client-preset] optional `' $fragmentName'` property

export type UserFieldsFragment = { __typename?: 'User', id: string, email: string, fullName: string, displayName: string, provider: AuthProvider, isAdmin: boolean }
  & { ' $fragmentName': 'UserFieldsFragment' };

The following:

{ ' $fragmentName': 'UserFieldsFragment' }

Should be:

{ ' $fragmentName'?: 'UserFieldsFragment' }

[ZakKa89]

Thank you I will try the new client preset. That might also solve this issue https://github.com/dotansimha/graphql-code-generator/issues/8474

[charlypoly]

Hi @ZakKa89,

the following code is found: `tweet: DocumentType

And I don’t understand we can’t just use tweet: TweetFragment

since that type is also available in the generated types, and has the types I need? Does that example help with understanding the question?

The fragment type is wrapped in a TypedDocumentNode<R,V> type, making it impossible to directly extract the inner type (the actual fragment type):

So are you I should use client-present over gql-tag-operations? I thought I read somewhere in the docs that gql-tag-operations was the preferred way right now, but can’t find it.

You are right, we only updated the guides for now: https://www.the-guild.dev/graphql/codegen/docs/guides/react-vue We plan to update the doc of gql-tag-operations and deprecate is on npm in the upcoming weeks.