dotansimha / dotansimha/graphql-code-generator-community
typescript-react-query: keep the possibility to define fetchParams when hardcoding the endpoint
- Dominant language
- TypeScript
- Stars
- 137
- Forks
- 195
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 16
Description
`
config: {
fetcher: {
endpoint: '/api'
),
},
},
`
This removes the possibility to set fetchParams when using the generated code.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the TypeScript React Query generator handles the fetcher configuration when an endpoint is hardcoded. Compare the generated configuration with the shown example and identify how fetchParams are currently lost. Done means fetchParams can still be defined alongside the hardcoded endpoint, with the relevant generator behavior covered by existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100