You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. The issue provides a reproduction available on GitHub, Stackblitz or CodeSandbox
Make sure to fork this template and run yarn generate in the terminal.
Please make sure the GraphQL Scalars package version under package.json matches yours.
2. A failing test has been provided
3. A local solution has been provided
4. A pull request is pending review
Describe the bug
The Latitude and Longitude codegen types are inconsistent. Latitude is string, Longitude is string | number. This results in inconsistent generated types in clients using graphql-codegen.
To Reproduce
Steps to reproduce the behavior:
Create a GraphQL schema using both latitude and longitude, then generate types using GraphQL Codegen. You will see latitude: string and longitude: string | number are the generated types.
Expected behavior
Latitude and Longitude should both generate the same types - probably string | number.
Environment:
OS: N/A
GraphQL Scalars Version: 1.22.2
NodeJS: v18
Additional context
If I have time, I'll submit a little PR to fix this.
The text was updated successfully, but these errors were encountered:
Issue workflow progress
Progress of the issue based on the Contributor Workflow
Describe the bug
The Latitude and Longitude codegen types are inconsistent. Latitude is
string
, Longitude isstring | number
. This results in inconsistent generated types in clients using graphql-codegen.To Reproduce
Steps to reproduce the behavior:
Create a GraphQL schema using both latitude and longitude, then generate types using GraphQL Codegen. You will see
latitude: string
andlongitude: string | number
are the generated types.Expected behavior
Latitude and Longitude should both generate the same types - probably
string | number
.Environment:
Additional context
If I have time, I'll submit a little PR to fix this.
The text was updated successfully, but these errors were encountered: