dotansimha / dotansimha/graphql-code-generator-community
typescript-react-query custom fetcher not using correct import with near-operation-file
- Dominant language
- TypeScript
- Stars
- 137
- Forks
- 195
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 16
Description
**Is your feature request related to a problem? Please describe.**
Using `near-oparation-file` has a wrong import using custom fetcher.
**Describe the solution you'd like**
The path should be correct.
**Describe alternatives you've considered**
Using typescript alias path fixes it but might be an easier fix within the plugin
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the typescript-react-query plugin's near-operation-file handling and reproduce generation with a custom fetcher; inspect the generated import path. Done means the generated custom-fetcher import resolves correctly without relying on a TypeScript alias path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100