Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Any interest in native go type support? #103

Open
schmidtw opened this issue Dec 4, 2022 · 1 comment
Open

Any interest in native go type support? #103

schmidtw opened this issue Dec 4, 2022 · 1 comment

Comments

@schmidtw
Copy link

schmidtw commented Dec 4, 2022

I see the shurcooL/githubv4 project is being updated (at one point in time it looked like this project was not).

Do you have any interested in directly supporting go native types like this?
hasura#45
@dmitshur
Copy link
Member

It is already possible to use predeclared Go types. It's not mentioned in this repo's README, but see the Scalar Types section of githubv4's README.

I did want to remove the GraphQL named types like graphql.String and graphql.Int during early development around 2017, see issue shurcooL/githubv4#9. It turned out hard to completely remove them because they can be useful for inputs/variables (see shurcooL/githubv4#9 (comment)). I haven't had free time to allocate to large open-ended issues here, so there hasn't been progress on this from my side since then.

alexandear pushed a commit to alexandear/graphql that referenced this issue Jan 8, 2024
@pontusntengnas @hgiasac
set the operation name to the request payload if exist (shurcooL#103)
1956215 
* set the operation name to the request payload if exist

---------

Co-authored-by: Toan Nguyen <hgiasac@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@schmidtw @dmitshur