apollographql / apollographql/apollo-tooling
Wanted: Ability to force-export fragments in generatedTypes
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 460
- PR merge metrics
- No merged PRs in 30d
Description
In our codebase `generatedTypes.ts` includes some useful fragments that are not being exported. I believe these are fragments that aren't defined manually in a `.gql` file and are auto-generated based on other fragment definitions, specifically some that use
`... on SomethingElse`
in their body, resulting in non-exported fragments like `Something_SomethingElse_Fragment`.
It would be really cool if there was a way to force `codegen` to export these as well.
Contributor guide
Research direction
Start by tracing the codegen path that produces generatedTypes.ts and inspect how fragments containing `... on SomethingElse` are classified for export. The work is done when there is a supported way to force those generated fragments, such as `Something_SomethingElse_Fragment`, to be exported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100