feat : [typescript-react-apollo] support useSuspenseQuery

[Hal-ang]

Description

Implemented useSuspenseQuery, which was added in apollo 3.8.0 version.

Related #388

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as
  expected)
• This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):

Adding links to sandbox or providing screenshots can help us understand more about this PR and take
action on it as appropriate

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can
reproduce. Please also list any relevant details for your test configuration

• I ran codegen with the changes applied to the project that is actually using the library, and confirmed that useSuspenseQuery was working properly. (with patch-package)
• passed yarn run test after update snapshot file

Test Environment:

• OS: Mac OS
• @graphql-codegen/[email protected]:
• NodeJS: 18.17.1

Checklist:

• I have followed the
  CONTRIBUTING doc and the
  style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[changeset-bot]

🦋 Changeset detected

Latest commit: 38d320a

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

This PR includes changesets to release 1 package

Name	Type
@graphql-codegen/typescript-react-apollo	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

[Hal-ang]

@saihaj
Hi, Could you review this PR? thx :D

[Hal-ang]

sorry. If I understand correctly, is it correct that the test failure of github action is resolved when the test code changes in my PR are merged? I'm not sure what part I need to fix separately. This is my first contribution, so please understand my lack of experience. 😭

[saihaj]

hey @Hal-ang can you please run yarn prettier . --write and then commit that. That should make the prettier check happy

for the failing tests you need to update all the snapshots I think

[Hal-ang]

Thanks! I pushed the new updated snapshot and prettier code

[Hal-ang]

HI, @saihaj :D
If you have a time, Could you please merge this PR? Thanks!

[saihaj]

@Hal-ang looks like tests are still failing. Are they passing for you locally?

[saihaj]

actually I reverted things and CI on main should pass. You should try syncing this branch with main and then that should make CI happy 🤞🏼 @Hal-ang

[Hal-ang]

actually I reverted things and CI on main should pass. You should try syncing this branch with main and then that should make CI happy 🤞🏼 @Hal-ang

Oh! Sorry for the late confirmation. thanks I tried to syncing a fork branch and checked test on my local :D

[saihaj]

hey @Hal-ang can you run yarn generate:examples and commit the changes?

[Hal-ang]

hey @Hal-ang can you run yarn generate:examples and commit the changes?

thank you I tried running that script and running 'yarn run test' from root. After that, I also confirmed that it was passed. However, I am worried because there is an import error in the created folder. 🥲

[Hal-ang]

It seems that the node-side settings of env in GitHub Actions do not work well. I'm not sure how to solve this, can you help me?

[fforres]

@saihaj @Hal-ang Really excited to see this feature :D
Anything the rest of us can do to help?
(Would love to use this as a base to add support to useBackgroundQuery 🙏, not sure what the state of the PR is)

[saihaj]

great work @Hal-ang!

[Brobin]

Can we please add to the release notes that this requires @apollo/client > 3.8?

[Grohden]

New feature (non-breaking change which adds functionality)

isn't this a breaking change since it now requires apollo >= 3.8 and we can't opt out of suspense generation stuff?