graphql-code-generator-community

graphql-code-generator-community copied to clipboard

🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.

Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Related # (issue)

Type of change

Please delete options that are not relevant.

• [x] New feature (non-breaking change which adds functionality)

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

• [x] yarn test
• [x] yarn build

Test Environment:

• OS:ubuntu 22
• @graphql-codegen/...:
• NodeJS: 18.16.0

Checklist:

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

Further comments

I have used @graphql-codegen/typescript-graphql-request, but the object generated by it is a large object, each method is a request funciton, it works but can not be treeshaked. I would like to use seperated export for each request function, the functions are not related to each other so they can be treeshaked.

I have read the contributing doc. I am confused in step 10. website/src/pages/plugins/ dir is in graphql-code-generator, will it be moved to graphql-code-generator-community ?

Should I publish the new plugin myself or by the community?

⚠️ No Changeset found

Latest commit: 9b3394298b68bfa56407403662514da483a191b4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@saihaj I'm coming here after looking for a similar solution. It looks like this functionality was added to the original repo, but was never reopened in this repo: https://github.com/dotansimha/graphql-code-generator/pull/8131