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.

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

Update GraphQL for .NET to latest #15104

Closed
Piedone opened this issue Jan 16, 2024 · 8 comments · Fixed by #15129
Closed

Update GraphQL for .NET to latest #15104

Piedone opened this issue Jan 16, 2024 · 8 comments · Fixed by #15129
Milestone

Comments

@Piedone
Copy link
Member

Piedone commented Jan 16, 2024

Is your feature request related to a problem? Please describe.

GraphQL for .NET is currently on v7.7.2 while we use 4.8.0. While this is not hugely old (it was released in March 2022) but it still is, and we're too much behind.

Describe the solution you'd like

Upgrade to the latest version. This will be a pain I'd guess. Perhaps we could ask somebody from the GraphQL for .NET team to help?

Describe alternatives you've considered

I really don't know of any.

@Piedone
Copy link
Member Author

Piedone commented Jan 16, 2024

Related: #12295.

@hishamco
Copy link
Member

hishamco commented Jan 16, 2024

I already have a PR #13255 but I might need help there because there're many breaking changes

@hyzx86 let me know if you can help me in the related PR

@hyzx86
Copy link
Contributor

hyzx86 commented Jan 16, 2024

@hishamco Wow, I just started researching Graphql.Relay recently

But its version relies on Graphql 7.x, so I tried to downgrade graphql.relay to an earlier version.

@hyzx86
Copy link
Contributor

hyzx86 commented Jan 16, 2024

@hyzx86 let me know if you can help me in the related PR

Let me have a look first.

@hyzx86
Copy link
Contributor

hyzx86 commented Jan 31, 2024

Done at #15129
it's ready to review

@ShaneCourtrille
Copy link
Contributor

@sebastienros Do you expect this to be included in 1.9? We're going to start working on performance issues and this is a requirement for that so trying to decide if we just pull this in by itself or not.

@sebastienros
Copy link
Member

It's merged, so this will be part of the next release, 1.9

@sebastienros
Copy link
Member

You can already use the main branch of the nightly feed to work with it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants