\u00d6ncelikle GraphQL<\/em> konusu,\u00a0benim i\u00e7inde yeni say\u0131labilecek bir konu. GraphQL<\/em> ile hen\u00fcz production \u00fczerinde bir tecr\u00fcbe edinemedim. Fakat yak\u0131n bir d\u00f6nem i\u00e7erisinde \u00f6zellikle mobile API’lar\u0131m\u0131z i\u00e7in bir gateway gibi\u00a0GraphQL<\/em> ile veri eri\u015fimi ve sorgulama i\u015flemlerini ger\u00e7ekle\u015ftirebilmeyi planl\u0131yoruz. (\u015euan \u00fczerinde \u00e7al\u0131\u015f\u0131yoruz)<\/p>\n Bu makale i\u00e7erisinde ise ASP.NET Core 2.0<\/em> ile GraphQL<\/em>‘i kullanarak, sorgulama i\u015flemlerini efficient bir \u015fekilde nas\u0131l ger\u00e7ekle\u015ftirebiliriz konusuna, ara\u015ft\u0131rmalar\u0131m s\u0131ras\u0131nda edinebildi\u011fim bilgiler do\u011frultusunda de\u011finmeye \u00e7al\u0131\u015faca\u011f\u0131m.<\/p>\n Neden GraphQL<\/em> sorusuna ge\u00e7meden \u00f6nce, bir konuya de\u011finmek istiyorum. Bir \u00e7ok ki\u015fi\u00a0REST<\/em>‘in \u00f6lece\u011fi ve GraphQL<\/em>‘in ise yeni gelecek oldu\u011fundan bahsediyor. Ben \u015fahsen bu fikre kat\u0131lm\u0131yorum. REST<\/em> ve GraphQL<\/em>‘in birbirleri ile kar\u0131\u015ft\u0131r\u0131lmamas\u0131 gerekti\u011fi d\u00fc\u015f\u00fcncesindeyim.<\/p>\n \u0130lk olarak hem\u00a0REST<\/em> hem de GraphQL<\/em>‘in bir arada kullan\u0131m\u0131 m\u00fcmk\u00fcnd\u00fcr. Ayr\u0131ca GraphQL\u00a0<\/em>do\u011fru zaman<\/strong> ve do\u011fru ihtiya\u00e7lar<\/strong> kar\u015f\u0131s\u0131nda kullan\u0131ld\u0131\u011f\u0131nda,\u00a0veri eri\u015fimi (\u00f6zellikle mobile taraf\u0131 i\u00e7in) ve querying konusunda client’lar i\u00e7in olduk\u00e7a esneklik sa\u011flamaktad\u0131r.<\/p>\n Peki, neden GraphQL<\/em> k\u0131sm\u0131na \u015f\u00f6yle bir giri\u015f yapay\u0131m. G\u00fcn\u00fcm\u00fcz teknolojisinde mobile uygulamalar\u0131n\u0131n kullan\u0131m oran\u0131n\u0131n, olduk\u00e7a fazla oldu\u011fu ortada. \u00c7al\u0131\u015fm\u0131\u015f oldu\u011fum firmalarda, online kullan\u0131c\u0131lar\u0131n bir \u00e7o\u011funu neredeyse mobile kullan\u0131c\u0131lar olu\u015fturmakta. Development taraf\u0131na bakt\u0131\u011f\u0131m\u0131zda ise uygulamalar\u0131m\u0131z\u0131n building block’lar\u0131n\u0131 olu\u015fturan API<\/em>‘lar\u0131, hem web hemde mobile taraflar\u0131 i\u00e7in kullanmaktay\u0131z.<\/p>\n \u0130\u015fte tam da bu noktada, \u00f6zellikle mobile taraf\u0131 i\u00e7in baz\u0131\u00a0challenge’lar ile kar\u015f\u0131la\u015fmaktay\u0131z. \u00c7\u00fcnk\u00fc mobile taraf\u0131 i\u00e7in al\u0131nan data boyutu, pil ve \u015febeke kullan\u0131m\u0131 gibi durumlar b\u00fcy\u00fck \u00f6nem ta\u015f\u0131maktad\u0131r. Genelde bu tarz challenge’lar\u0131,\u00a0API<\/em>‘lar\u0131n \u00f6n\u00fcne Gateway API<\/strong>‘lar yazarak aggregation i\u015flemlerini gateway i\u00e7erisinde ger\u00e7ekle\u015ftirip, developer’\u0131n istedi\u011fi data’lar\u0131 filtreleyerek alabilmesi ile atlat\u0131r\u0131z. Kula\u011fa ho\u015f gelse de, ne yaz\u0131k ki i\u015f burada bitmiyor. :) Bununla birlikte versiyonlama<\/em>\u00a0ve\u00a0backward compatibility<\/em>\u00a0gibi\u00a0vb. challenge’larla da kar\u015f\u0131la\u015fmak durumunda kalabiliyoruz.<\/p>\n \u0130\u015fte bu gibi durumlar kar\u015f\u0131s\u0131nda GraphQL<\/em>‘in bizlere sundu\u011fu a\u015fa\u011f\u0131daki gibi baz\u0131 avantajlar bulunmaktad\u0131r.<\/p>\n H\u0131zl\u0131 ve kolay development konusundan biraz bahsetmek gerekirse e\u011fer, bir \u00e7ok kurum i\u00e7erisinde development ekipleri k\u00fc\u00e7\u00fck domain’lere g\u00f6re b\u00f6l\u00fcn\u00fcp, her ekip kendi sorumlulu\u011funun bulundu\u011fu uygulamalar\u0131 geli\u015ftirmektedir. Benim \u00e7al\u0131\u015ft\u0131\u011f\u0131m bir ka\u00e7 firmada bu \u015fekildeydi.<\/p>\n D\u00fc\u015f\u00fcnelim, \u00fcr\u00fcn detay sayfas\u0131nda “1<\/em>” numaral\u0131 \u00fcr\u00fcn\u00fcn detay bilgilerine ihtiyac\u0131m\u0131z var. Bir\u00a0RESTful<\/em>\u00a0API\u00a0<\/em>i\u00e7erisinde normal \u015fartlarda bu bilgileri “api\/products\/1<\/em>” \u015feklinde bir endpoint’e GET<\/em> iste\u011finde bulunarak, kolayl\u0131kla eri\u015febiliriz. Mobile ekibin ise bu \u00fcr\u00fcn bilgilerinden sadece “name<\/em>“, “description<\/em>” ve “price<\/em>” field’lar\u0131na ihtiyac\u0131 olup, bunlara ek olarak birde \u00fcr\u00fcn\u00fcn kategori bilgilerine\u00a0de ihtiyac\u0131 oldu\u011funu varsayal\u0131m.<\/p>\n Bu tarz durumlar kar\u015f\u0131s\u0131nda, yapabilece\u011fimiz iki farkl\u0131 se\u00e7enek bulunmaktad\u0131r.<\/p>\n Bunlara ek olarak birde her ekibin kendi sprint’lerini ko\u015ftu\u011funu varsayarsak, mobile ekip bu noktada “Product”\u00a0API<\/em>‘\u0131ndan sorumlu ekibin ilgili development’\u0131 yapmas\u0131n\u0131 da bekleyecektir. H\u0131zla yeni feature’lar eklemek istedi\u011fimiz bu teknoloji pazar\u0131nda ise, beklemek \u00e7ok da ho\u015f olmayacakt\u0131r, de\u011fil mi?<\/p>\n GraphQL <\/em>ile bir API<\/em> tasarland\u0131\u011f\u0131nda ise, mobile ekip di\u011fer ekiplere ba\u011f\u0131ml\u0131 olmadan istedi\u011fi data’y\u0131 tek bir request ile efficient bir \u015fekilde sorgulayarak alabilmesi, h\u0131zl\u0131 bir \u015fekilde ihtiya\u00e7lar\u0131na g\u00f6re development i\u015flemlerini ger\u00e7ekle\u015ftirebilmesi kolay bir hale gelmektedir.<\/p>\n \u00d6rnek bir GraphQL<\/em> query’sine bakmak istersek e\u011fer:<\/p>\n Yukar\u0131daki gibi single bir query ile istenilen data, client-driven generated bir \u015fekilde kolayl\u0131kla al\u0131nabilmektedir.<\/p>\n NOT<\/strong>: Bu i\u015flemleri elbette bir RESTful API<\/em> ile de yapabilmek m\u00fcmk\u00fcnd\u00fcr. (Querying, filtering, sorting, vb…) Fakat her yeni bir ihtiya\u00e7 kar\u015f\u0131s\u0131nda istenilen feature’\u0131n, RESTful API<\/em>‘a implemente edilmesi veya client taraf\u0131nda handle edilmesi gerekmektedir. (Roundtrips!)\u00a0GraphQL<\/em> bu noktada \u00f6n plana \u00e7\u0131karken, unutmamal\u0131y\u0131z ki GraphQL<\/em>‘in istenilenleri ger\u00e7ekle\u015ftirebilmesi i\u00e7in ise, do\u011fru bir mapping yap\u0131s\u0131na da sahip olmas\u0131 gerekmektedir.<\/p><\/blockquote>\n Implementasyon a\u015famas\u0131nda ise, \u00f6rnek olarak basit bir “\u00fcr\u00fcn” ve “kategori” i\u00e7eren bir API<\/em> tasarlayaca\u011f\u0131z.<\/p>\n Bunun i\u00e7in \u00f6ncelikle a\u015fa\u011f\u0131daki komut sat\u0131r\u0131 ile yeni bir ASP.NET Core<\/em>\u00a0“webapi”<\/strong> projesi olu\u015ftural\u0131m.<\/p>\n Projenin olu\u015fturulmas\u0131ndan sonra “Models<\/em>” isminde bir klas\u00f6r olu\u015fturarak, “Category<\/em>” ve “Product<\/em>” model’lerini burada tan\u0131mlayal\u0131m.<\/p>\n Modelleri tan\u0131mlaman\u0131n ard\u0131ndan “Data<\/em>” isimli bir klas\u00f6r daha olu\u015ftural\u0131m. \u0130\u00e7erisinde ise “ICategoryRepository<\/em>” ve “IProductRepository<\/em>” interface’lerini a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m.<\/p>\n Bu interface’lerin implementasyonlar\u0131n\u0131 ise, test data’lar\u0131 ile birlikte a\u015fa\u011f\u0131daki gibi ger\u00e7ekle\u015ftirelim.<\/p>\n Model ve repository’ler haz\u0131r oldu\u011funa g\u00f6re, art\u0131k GraphQL<\/strong>‘in .NET<\/em> client’\u0131n\u0131 implemente etmeye ba\u015flayabiliriz.<\/p>\n Bunun i\u00e7in \u00f6ncelikle a\u015fa\u011f\u0131daki komutu kullanarak, projemize GraphQL<\/em> paketini NuGet<\/em> \u00fczerinden dahil edelim.<\/p>\n Paketi projemize ekledikten sonra, ilk olarak GraphQL Object Type<\/strong>‘lar\u0131n\u0131 tan\u0131mlamaya ba\u015flayal\u0131m.\u00a0 Object type<\/em>‘lar\u0131 ve field’<\/em>lar GraphQL<\/em> schema’s\u0131n\u0131n en temel bile\u015fenlerini olu\u015fturmaktad\u0131r. Yani, olu\u015fturaca\u011f\u0131m\u0131z servis \u00fczerinden hangi objeleri alabilece\u011fimizi ve hangi field’lara sahip oldu\u011funu belirtmektedir.<\/p>\n Bu \u00f6n bilginin ard\u0131ndan “Models<\/em>” klas\u00f6r\u00fc i\u00e7erisinde, “CategoryType<\/em>” ve “ProductType<\/em>” class’lar\u0131n\u0131 da a\u015fa\u011f\u0131daki gibi olu\u015ftural\u0131m.<\/p>\n Dikkat edersek her iki class da, “ObjectGraphType<\/em>” class’\u0131ndan t\u00fcretilmektedir. Sonras\u0131nda ise constructor i\u00e7erisinden GraphQL<\/em> paketinin fluent method’lar\u0131n\u0131 kullanarak, hangi field’lara sahip olmas\u0131 gerekti\u011fini expression’lar ile tan\u0131mlad\u0131k. Ard\u0131ndan relation field’lar\u0131 i\u00e7in ise resolve function’lar\u0131n\u0131 yazd\u0131k.<\/p>\n \u015eimdi query i\u015flemleri i\u00e7in kullanacak oldu\u011fumuz root type’\u0131 olu\u015fturaca\u011f\u0131z. Bunun i\u00e7in “EasyStoreQuery<\/em>” isminde yeni bir class tan\u0131mlayal\u0131m ve a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n “EasyStoreQuery<\/em>” root type’\u0131 i\u00e7erisinde, “CategoryType<\/em>” ve “ProductType<\/em>” da oldu\u011fu gibi constructor i\u00e7erisinde schema’y\u0131 configure ettik. Configure i\u015flemi s\u0131ras\u0131nda “arguments<\/strong>” parametresi ile ise, ilgili field’\u0131n hangi argument’ler do\u011frultusunda al\u0131nabilece\u011fini belirttik.<\/p>\n NOT<\/strong>: “CategoryType<\/em>“, “ProductType<\/em>” ve “EasyStoreQuery<\/em>” i\u00e7erisindeki resolve function’lar\u0131n\u0131n source’u olarak “category” ve “product” repository’lerini configure etmek yerine, “category” ve ya “product” i\u00e7in olan ilgili\u00a0REST <\/em>endpoint’lerini de\u00a0<\/em>configure edebilirdik.<\/p><\/blockquote>\n Art\u0131k d\u0131\u015far\u0131ya expose edecek oldu\u011fumuz data’m\u0131z\u0131n, structure’\u0131n\u0131 tan\u0131mlayacak olan schema’y\u0131 olu\u015fturabiliriz. Bunun i\u00e7in “EasyStoreSchema<\/em>” ad\u0131nda bir class daha olu\u015ftural\u0131m ve “Schema<\/em>” class’\u0131ndan t\u00fcreterek, a\u015fa\u011f\u0131daki gibi kodlayal\u0131m.<\/p>\n Bir schema’n\u0131n sahip olabilece\u011fi iki adet\u00a0temel type bulunmaktad\u0131r. Bunlardan ilki “Query”, di\u011feri ise “Mutation” type’\u0131d\u0131r. Biz ise burada sadece “Query” type’\u0131n\u0131 kulland\u0131k. “EasyStoreSchema<\/em>” class’\u0131n\u0131\u00a0DI<\/strong> container \u00fczerinden inject ederken, resolve type olarak ise “EasyStoreQuery<\/em>” type’\u0131n\u0131 parametre olarak ge\u00e7ece\u011fiz.<\/p>\n Art\u0131k geriye yapmam\u0131z gereken iki \u015fey kald\u0131. Bunlardan ilki GraphQL endpoint’ini haz\u0131rlamak, bir di\u011feri de service injection i\u015flemlerini ger\u00e7ekle\u015ftirmek. Endpoint’i haz\u0131rlamak i\u00e7in \u00f6ncelikle “Models<\/em>” klas\u00f6r\u00fc i\u00e7erisinde “GraphQLQuery<\/em>” isminde bir request class’\u0131 olu\u015ftural\u0131m ve a\u015fa\u011f\u0131daki gibi tan\u0131mlayal\u0131m.<\/p>\n Request objesini tan\u0131mlaman\u0131n ard\u0131ndan, “Controllers<\/em>” klas\u00f6r\u00fc i\u00e7erisinde ise “GraphQLController<\/em>” isminde bir controller class’\u0131 ekleyerek kodlamaya ba\u015flayal\u0131m.<\/p>\n \u0130lk olarak “Route<\/em>” attribute’\u00fc ile endpoint’i belirledik ve ard\u0131ndan “IDocumentExecuter<\/em>” ve “ISchema<\/em>” interface’lerinin inject i\u015flemlerini ger\u00e7ekle\u015ftirdik. Bu noktada “IDocumentExecuter<\/em>“, “ExecutionOptions<\/em>” parametresini execute ederek, client’\u0131n istemi\u015f oldu\u011fu data’y\u0131 olu\u015fturacakt\u0131r. Bu noktada, client-driven application development yapabilmek, \u00e7ok da ho\u015f de\u011fil mi?<\/p>\n Art\u0131k geriye sadece dependency injection i\u015flemi kald\u0131. “Startup<\/em>” class’\u0131 i\u00e7erisinde injection i\u015flemlerini a\u015fa\u011f\u0131daki gibi ger\u00e7ekle\u015ftirelim.<\/p>\n \u0130\u015fte hepsi bu kadar.<\/p>\n \u015eimdi terminal \u00fczerinden “dotnet run<\/em>” komutunu \u00e7al\u0131\u015ft\u0131rarak, bir ka\u00e7 test yapabiliriz.<\/p>\n NOT<\/strong>: Ben test i\u015flemleri i\u00e7in “Postman<\/em>” kullanaca\u011f\u0131m.<\/p><\/blockquote>\n A\u015fa\u011f\u0131daki sorguyu GraphQL<\/em> endpoint’ine, POST<\/strong>\u00a0olarak g\u00f6nderelim ve sonucunu g\u00f6relim.<\/p>\n Response’a bakt\u0131\u011f\u0131m\u0131zda ise a\u015fa\u011f\u0131da g\u00f6rd\u00fc\u011f\u00fcm\u00fcz gibi, “1<\/em>” numaral\u0131 kategoriye ait “id<\/em>” ve “name<\/em>” field’lar\u0131 gelmi\u015ftir.<\/p>\n Sonucu ise a\u015fa\u011f\u0131daki gibi ortada.<\/p>\n GraphQL<\/em> ile PoC<\/em> yaparken ger\u00e7ekten \u00e7ok keyif ald\u0131m. Bu konudaki benim fikrim ise, e\u011fer database schema’m\u0131z ve ya API<\/em> design’lar\u0131m\u0131z resource olarak kullan\u0131lmaya uygun ise, GraphQL’<\/em>i implemente etmek\u00a0\u00f6zellikle client-driven application development<\/strong> i\u00e7in do\u011fru bir tercih olacakt\u0131r. Ayr\u0131ca GraphQL client’a sadece istedi\u011fi \u00f6l\u00e7\u00fcde data’y\u0131 verebilmesiyle beraber, server ile client aras\u0131ndaki veri boyutunun k\u00fc\u00e7\u00fclmesini de sa\u011flamaktad\u0131r.<\/p>\n![\"\"](\"\/wp-content\/uploads\/2017\/11\/FastEnough.jpg\")
<\/a><\/p>\nPeki, Neden GraphQL?<\/h5>\n
<\/a><\/p>\n<\/a><\/p>\n\n
<\/a><\/p>\n\n
{\r\n product(id: 1){\r\n name\r\n description\r\n price\r\n category{\r\n id\r\n name\r\n }\r\n }\r\n}<\/pre>\nASP.NET Core 2.0 ile Implementasyon<\/h5>\n
mkdir aspnetcoregarphql\r\ncd aspnetcoregarphql\r\ndotnet new webapi<\/pre>\n
namespace aspnetcoregraphql.Models\r\n{\r\n public class Category\r\n {\r\n public int Id { get; set; }\r\n public string Name { get; set; }\r\n\r\n List<Product> Products { get; set; }\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Models\r\n{\r\n public class Product\r\n {\r\n public int Id { get; set; }\r\n public int CategoryId { get; set; }\r\n public string Name { get; set; }\r\n public string Description { get; set; }\r\n public double Price { get; set; }\r\n\r\n Category Category { get; set;}\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Data\r\n{\r\n public interface ICategoryRepository\r\n {\r\n Task<List<Category>> CategoriesAsync();\r\n Task<Category> GetCategoryAsync(int id);\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Data\r\n{\r\n public interface IProductRepository\r\n {\r\n Task<List<Product>> GetProductsAsync();\r\n Task<List<Product>> GetProductsWithByCategoryIdAsync(int categoryId);\r\n Task<Product> GetProductAsync(int id);\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Data\r\n{\r\n public class CategoryRepository : ICategoryRepository\r\n {\r\n private List<Category> _categories;\r\n\r\n public CategoryRepository()\r\n {\r\n _categories = new List<Category>{\r\n new Category()\r\n {\r\n Id = 1,\r\n Name = \"Computers\"\r\n },\r\n new Category()\r\n {\r\n Id = 2,\r\n Name = \"Mobile Phones\"\r\n }\r\n };\r\n }\r\n\r\n public Task<List<Category>> CategoriesAsync()\r\n {\r\n return Task.FromResult(_categories);\r\n }\r\n\r\n public Task<Category> GetCategoryAsync(int id)\r\n {\r\n return Task.FromResult(_categories.FirstOrDefault(x => x.Id == id));\r\n }\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Data\r\n{\r\n public class ProductRepository : IProductRepository\r\n {\r\n private List<Product> _products;\r\n\r\n public ProductRepository()\r\n {\r\n _products = new List<Product>{\r\n new Product()\r\n {\r\n Id = 1,\r\n CategoryId = 1,\r\n Name = \"Apple Macbook Pro 2016\",\r\n Description = \"Touchbar, 3.2GHZ\",\r\n Price = 5000\r\n },\r\n new Product()\r\n {\r\n Id = 2,\r\n CategoryId = 1,\r\n Name = \"Apple Macbook Air\",\r\n Description = \"2.3GHZ 8GB RAM\",\r\n Price = 2000\r\n },\r\n new Product()\r\n {\r\n Id = 3,\r\n CategoryId = 1,\r\n Name = \"Dell XPS 13\",\r\n Description = \"3.3GHZ 12GB RAM\",\r\n Price = 4000\r\n }\r\n };\r\n }\r\n\r\n public Task<Product> GetProductAsync(int id)\r\n {\r\n return Task.FromResult(_products.FirstOrDefault(x => x.Id == id));\r\n }\r\n\r\n public Task<List<Product>> GetProductsAsync()\r\n {\r\n return Task.FromResult(_products);\r\n }\r\n \r\n public Task<List<Product>> GetProductsWithByCategoryIdAsync(int categoryId)\r\n {\r\n return Task.FromResult(_products.Where(x => x.CategoryId == categoryId).ToList());\r\n }\r\n }\r\n}<\/pre>\ndotnet add package GraphQL<\/pre>\n
namespace aspnetcoregraphql.Models\r\n{\r\n public class CategoryType : ObjectGraphType<Category>\r\n {\r\n public CategoryType(IProductRepository productRepository)\r\n {\r\n Field(x => x.Id).Description(\"Category id.\");\r\n Field(x => x.Name, nullable: true).Description(\"Category name.\");\r\n\r\n Field<ListGraphType<ProductType>>(\r\n \"products\", \r\n resolve: context => productRepository.GetProductsWithByCategoryIdAsync(context.Source.Id).Result.ToList()\r\n );\r\n }\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Models\r\n{\r\n public class ProductType : ObjectGraphType<Product>\r\n {\r\n public ProductType(ICategoryRepository categoryRepository)\r\n {\r\n Field(x => x.Id).Description(\"Product id.\");\r\n Field(x => x.Name).Description(\"Product name.\");\r\n Field(x => x.Description, nullable: true).Description(\"Product description.\");\r\n Field(x => x.Price).Description(\"Product price.\");\r\n\r\n Field<CategoryType>(\r\n \"category\", \r\n resolve: context => categoryRepository.GetCategoryAsync(context.Source.CategoryId).Result\r\n );\r\n }\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Models\r\n{\r\n public class EasyStoreQuery : ObjectGraphType\r\n {\r\n public EasyStoreQuery(ICategoryRepository categoryRepository, IProductRepository productRepository)\r\n {\r\n Field<CategoryType>(\r\n \"category\",\r\n arguments: new QueryArguments(\r\n new QueryArgument<NonNullGraphType<IntGraphType>> {Name = \"id\", Description = \"Category id\"}\r\n ),\r\n resolve: context => categoryRepository.GetCategoryAsync(context.GetArgument<int>(\"id\")).Result\r\n );\r\n\r\n Field<ProductType>(\r\n \"product\",\r\n arguments: new QueryArguments(\r\n new QueryArgument<NonNullGraphType<IntGraphType>> {Name = \"id\", Description = \"Product id\"}\r\n ),\r\n resolve: context => productRepository.GetProductAsync(context.GetArgument<int>(\"id\")).Result\r\n );\r\n }\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Models\r\n{\r\n public class EasyStoreSchema : Schema\r\n {\r\n public EasyStoreSchema(Func<Type, GraphType> resolveType)\r\n :base(resolveType)\r\n {\r\n Query = (EasyStoreQuery)resolveType(typeof(EasyStoreQuery));\r\n }\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Models\r\n{\r\n public class GraphQLQuery\r\n {\r\n public string OperationName { get; set; }\r\n public string NamedQuery { get; set; }\r\n public string Query { get; set; }\r\n public string Variables { get; set; }\r\n }\r\n}<\/pre>\nnamespace aspnetcoregraphql.Controllers\r\n{\r\n [Route(\"graphql\")]\r\n public class GraphQLController : Controller\r\n {\r\n private readonly IDocumentExecuter _documentExecuter;\r\n private readonly ISchema _schema;\r\n\r\n public GraphQLController(IDocumentExecuter documentExecuter,ISchema schema)\r\n {\r\n _documentExecuter = documentExecuter;\r\n _schema = schema;\r\n }\r\n\r\n [HttpPost]\r\n public async Task<IActionResult> Post([FromBody]GraphQLQuery query)\r\n {\r\n if (query == null) { throw new ArgumentNullException(nameof(query)); }\r\n\r\n var executionOptions = new ExecutionOptions { Schema = _schema, Query = query.Query };\r\n\r\n try\r\n {\r\n var result = await _documentExecuter.ExecuteAsync(executionOptions).ConfigureAwait(false);\r\n\r\n if (result.Errors?.Count > 0)\r\n {\r\n return BadRequest(result);\r\n }\r\n\r\n return Ok(result);\r\n }\r\n catch(Exception ex)\r\n {\r\n return BadRequest(ex);\r\n }\r\n }\r\n }\r\n}<\/pre>\npublic void ConfigureServices(IServiceCollection services)\r\n{\r\n services.AddMvc();\r\n\r\n services.AddScoped<EasyStoreQuery>(); \r\n services.AddTransient<ICategoryRepository, CategoryRepository>();\r\n services.AddTransient<IProductRepository, ProductRepository>(); \r\n services.AddScoped<IDocumentExecuter, DocumentExecuter>();\r\n services.AddTransient<CategoryType>();\r\n services.AddTransient<ProductType>();\r\n var sp = services.BuildServiceProvider();\r\n services.AddScoped<ISchema>(_ => new EasyStoreSchema(type => (GraphType) sp.GetService(type)) {Query = sp.GetService<EasyStoreQuery>()});\r\n}<\/pre>\n{ \r\n \"query\":\r\n \"query{\r\n category(id:1){\r\n id \r\n name\r\n }\r\n }\"\r\n}<\/pre>\n<\/a>Peki ya bu kategoriye ait \u00fcr\u00fcnleri, “id<\/em>“, “name<\/em>“, ve “price<\/em>” field’lar\u0131 ile gelmesini de istiyorsak, bu durumda ne olacak? Gayet basit. Tek yapmam\u0131z gereken, sorgumuzu a\u015fa\u011f\u0131daki gibi g\u00fcncellemek olacakt\u0131r.<\/p>\n{ \r\n \"query\":\r\n \"query{\r\n category(id:1){\r\n id \r\n name\r\n products{\r\n \tid\r\n \tname\r\n \tprice\r\n }\r\n }\r\n }\"\r\n}<\/pre>\n<\/a>Sonu\u00e7<\/h5>\n