_This issue has been moved from a ticket on Developer Community._
I'd suggest to make GraphQL functionalities a part of .NET (System.Net.Http.GraphQL).
There are community projects for it, like you can see here https://graphql.org/code/#c-net, but the demand for GraphQL is increasing. Having buil-it GraphQL classes and methods would provide a covenient way to build an API with a GraphQL endpoint. For instance there could be a template for a WebApi with GraphQL.
Original Comments
Feedback Bot on 8/3/2020, 03:17 AM:
Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. We'll provide an update once the issue has been triaged by the product team.
vsfeedback
All 7 comments
Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.
![msftbot[bot] picture](https://avatars2.githubusercontent.com/in/26612?v=4&s=40)
msftbot[bot]
on 5 Aug 2020
@JeremyLikness is doing some investigation about the maturity of GraphQL libraries on .NET. As a general rule, we want to strengthen the general .NET Library ecosystem so that there are great, trustworthy libraries to fulfil all needs. Only in certain cases is the best answer to put an implementation in the base .NET libraries.
danmosemsft
on 5 Aug 2020
We would need an actual API proposal as well :)
scalablecory
on 6 Aug 2020
I wouldn't suggest to put in the work to make an API proposal without consensus here that we would be open to it. As I suggested above we would rather support our ecosystem and that's what @JeremyLikness is looking into.
danmosemsft
on 6 Aug 2020
Looping in @jamesmontemagno who is doing focused work here as well. As @danmosemsft mentioned, right now we aren't looking to build System.GraphQL. We are in the process of evaluating existing libraries and speaking with customers to understand what their end-to-end scenarios are and where the pain points in .NET exist. That will drive our next steps to determine how we can help deliver the best experience for .NET developers.
JeremyLikness
on 6 Aug 2020
@ajcvickers where do you plan to track issues relating to GraphQL work (if any)?
danmosemsft
on 7 Dec 2020
@danmosemsft Not decided yet.
ajcvickers
on 7 Dec 2020
Related issues
noahfalk
路
3Comments
btecu
路
3Comments
chunseoklee
路
3Comments
jchannon
路
3Comments
nalywa
路
3Comments
Most helpful comment
@JeremyLikness is doing some investigation about the maturity of GraphQL libraries on .NET. As a general rule, we want to strengthen the general .NET Library ecosystem so that there are great, trustworthy libraries to fulfil all needs. Only in certain cases is the best answer to put an implementation in the base .NET libraries.