Yahut cinsiyete, ya\u015fa vs. gibi aramalar yapmak istersek de a\u015fa\u011f\u0131daki gibi metotlar e\u015fli\u011finde \u00e7al\u0131\u015fmam\u0131z\u0131 ger\u00e7ekle\u015ftirebiliriz.<\/p>\n
\r\nclass PersonRepository\r\n{\r\n    public IReadOnlyList<Person> GetByCreatedDate(DateTime minCreatedDate)\r\n    {\r\n        \/\/...\r\n    }\r\n    public IReadOnlyList<Person> GetByAge(int age)\r\n    {\r\n        \/\/...\r\n    }\r\n    public IReadOnlyList<Person> GetByGender(Gender gender)\r\n    {\r\n        \/\/...\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nArama kriterleri bu \u015fekilde tekil olarak de\u011ferlendirildi\u011finde rahatl\u0131kla ayr\u0131 metotlar \u00fczerinde bu i\u015flemleri ger\u00e7ekle\u015ftirebilmekteyiz. Amma velakin, bu kriterleri birle\u015ftirmeye karar verdi\u011fimizde i\u015flerimiz biraz daha karma\u015f\u0131kla\u015facakt\u0131r.<\/p>\n
Tabi, t\u00fcm arama kriterlerini k\u00fcm\u00fclatif olarak bar\u0131nd\u0131ran a\u015fa\u011f\u0131daki gibi bir metot geli\u015ftirerek de bu ihtiyac\u0131 rahatl\u0131kla kar\u015f\u0131layabiliriz.<\/p>\n
\n\r\nclass PersonRepository\r\n{\r\n    public IReadOnlyList<Person> Find(DateTime? minCreatedDate = null, int? age, Gender? gender = null)\r\n    {\r\n        \/\/...\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nElbet bu metoda da daha fazla kriter ekleyerek geni\u015fletebiliriz. Evet, kriterleri b\u00fct\u00fcnle\u015fik olarak bu metotla kar\u015f\u0131layarak ihtiya\u00e7lar\u0131m\u0131z\u0131 b\u00f6ylece giderebiliriz ama bu y\u00f6ntemin sizlerin de i\u00e7ine sinmedi\u011fini biliyorum \ud83d\ude42<\/p>\n
\u0130\u00e7eri\u011fimizin devam\u0131nda buradaki ihtiya\u00e7lar\u0131 daha ideal bir \u015fekilde kar\u015f\u0131layabilmemizi sa\u011flayacak olan Specification pattern yakla\u015f\u0131m\u0131yla ele al\u0131yor olaca\u011f\u0131z. \u015eimdilik \u00f6rnek senaryoyu biraz daha a\u00e7maya devam edelim.<\/p>\n
Bazen yap\u0131lan \u00e7al\u0131\u015fmalarda hedef verileri veritaban\u0131ndan \u00e7ektikten sonra da in-memory’de do\u011frulamalar ger\u00e7ekle\u015ftirmemiz gerekebilmektedir. \u00d6rne\u011fin, bir person’\u0131 herhangi bir g\u00f6reve tabi tutmadan \u00f6nce ya\u015f\u0131n\u0131n bu g\u00f6rev i\u00e7in uygun olup olmad\u0131\u011f\u0131n\u0131 do\u011frulamak isteriz.<\/p>\n
\n\r\nclass PersonService\r\n{\r\n    PersonRepository _personRepository = new();\r\n    public bool AssignToPerson(int personId)\r\n    {\r\n        Person person = _personRepository.GetById(personId);\r\n        if (person.Age < 18)\r\n            throw new Exception("The person is not eligible for task.");\r\n\r\n        return true;\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nBenzer \u015fekilde ayn\u0131 kriteri kar\u015f\u0131layan di\u011fer person’lar\u0131 da veritaban\u0131ndan sorgulamakta isteyebiliriz. Bunun i\u00e7in de a\u015fa\u011f\u0131daki gibi repository s\u0131n\u0131f\u0131nda bir i\u015flem uygulayabiliriz.<\/p>\n
\n\r\nclass PersonRepository\r\n{\r\n    public IReadOnlyList<Person> FindPeopleFitForTheJob()\r\n    {\r\n        return dbContext.Where(person => person.Age > 18).ToList();\r\n    }\r\n}\r\n<\/pre>\n<\/div>\n\u015eimdi burada durup, yapm\u0131\u015f oldu\u011fumuz i\u015flemleri de\u011ferlendirirsek e\u011fer bir person ile ilgili i\u015f kurallar\u0131 ve domain bilgisi gere\u011fi farkl\u0131 davran\u0131\u015flar\u0131 farkl\u0131 s\u0131n\u0131flar ve metotlar \u00fczerinde tan\u0131mlamak zorunda kald\u0131\u011f\u0131m\u0131z\u0131 g\u00f6r\u00fcyorsunuz. Ve hatta bu s\u0131n\u0131flar da Don\u2019t Repeat Yourself(DRY)<\/em> ilkesini ihlal ederek ister istemez tekrarl\u0131 i\u015flemler ger\u00e7ekle\u015ftirebiliyoruz. \u0130\u015fte Specification pattern’\u0131n bizlere yard\u0131mc\u0131 olabilece\u011fi yer tam da buras\u0131d\u0131r.<\/p>\n
Specification pattern, farkl\u0131 \u015fartlara ba\u011fl\u0131 olacak \u015fekilde de\u011ferlendirmelerde bulunabilecek ya da bir ba\u015fka deyi\u015fle de\u011ferlendirmeleri tam olarak nas\u0131l ay\u0131rt edebilece\u011fini bilecek s\u0131n\u0131flar tan\u0131mlamam\u0131z\u0131 ve domain bilgisi gere\u011fi t\u00fcrl\u00fc i\u015f kurallar\u0131n\u0131 bu s\u0131n\u0131flar \u00fczerinden uygulamam\u0131z\u0131 savunan bir tasar\u0131m desenidir.<\/em><\/p><\/blockquote>\n
Misal olarak a\u015fa\u011f\u0131daki gibi i\u015fe uygun olan person’lar\u0131 ifade eden bir \u015fartname olarak ‘PeopleFitForTheJobSpecification’ s\u0131n\u0131f\u0131n\u0131 tan\u0131mlayabiliriz.<\/p>\n
\n\r\nclass PeopleFitForTheJobSpecification : Specification<Person>\r\n{\r\n    public override Expression<Func<Person, bool>> ToExpression()\r\n    {\r\n        return p => p.Age > 18;\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nBiliyorum, base class olarak kullan\u0131lan Specification<T><\/code> s\u0131n\u0131f\u0131n\u0131n nereden geldi\u011fini merak ediyorsunuz. Zaten i\u015fin t\u00fcm detay\u0131 orada \ud83d\ude42 Onu ilerideki sat\u0131rlar\u0131m\u0131zda ayr\u0131ca konu\u015fuyor olaca\u011f\u0131z. \u015eimdilik bu specification ile farkl\u0131 s\u0131n\u0131flarda tekrar eden i\u015f kurallar\u0131n\u0131n nas\u0131l merkezi hale getirildi\u011fini g\u00f6rerek devam edelim.<\/p>\n
\n\r\nclass PersonService\r\n{\r\n    PersonRepository _personRepository = new();\r\n    public bool AssignToPerson(int personId)\r\n    {\r\n        Person person = _personRepository.GetById(personId);\r\n\r\n        PeopleFitForTheJobSpecification specification = new();\r\n\r\n        if (!specification.IsSatisfiedBy(person))\r\n            throw new Exception("The person is not eligible for task.");\r\n\r\n        return true;\r\n    }\r\n}\r\n<\/pre>\n<\/div>\n\n\r\nclass PersonRepository\r\n{\r\n    public IReadOnlyList<Person> FindPeopleFitForTheJob()\r\n    {\r\n        PeopleFitForTheJobSpecification specification = new();\r\n        return dbContext.Where(person => specification.IsSatisfiedBy(person)).ToList();\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nDikkat ederseniz bu yakla\u015f\u0131m yaln\u0131zca i\u015f kurallar\u0131n\u0131n ve domain bilgisi gere\u011fi farkl\u0131 davran\u0131\u015flar\u0131n tekrarlar\u0131n\u0131 ortadan kald\u0131rmakla kalmamakta, ayn\u0131 zamanda birden \u00e7ok \u00f6zelli\u011fin birle\u015ftirilmesine de olanak sa\u011flayabilecek bir altyap\u0131 sunmaktad\u0131r. B\u00f6ylece olduk\u00e7a karma\u015f\u0131k arama ve do\u011frulama kriterlerini kolayca olu\u015fturmam\u0131za yard\u0131mc\u0131 olmaktad\u0131r.<\/p>\n
Buradan yola \u00e7\u0131karak \u015f\u00f6yle bir genellemeye varabiliriz ki, Specification pattern iki ana noktada kullan\u0131ma sunulabilmektedir;<\/p>\n
\nVeritaban\u0131ndan elimizdeki specification’a uyan hedef verileri sorgularken.<\/em><\/li>\n
Veritaban\u0131ndan sorgu neticesinde gelen veya d\u0131\u015f bir servis taraf\u0131ndan g\u00f6nderilen yahut kendimizce create edilen herhangi bir nesnenin ya da nesnelerin i\u015f kurallar\u0131na uyup uymad\u0131\u011f\u0131n\u0131 in-memory’de kontrol ederken.<\/em><\/li>\n<\/ul>\nSpecification Pattern Nas\u0131l Uygulan\u0131r?<\/h4>\nAsl\u0131nda specification pattern’\u0131n i\u015f kurallar\u0131n\u0131 bar\u0131nd\u0131ran s\u0131n\u0131flar ile uygulanaca\u011f\u0131n\u0131 yukar\u0131daki sat\u0131rlar\u0131m\u0131zda yapt\u0131\u011f\u0131m\u0131z izahatlerden anlam\u0131\u015fs\u0131n\u0131zd\u0131r diye d\u00fc\u015f\u00fcn\u00fcyorum. Biz yine de olay\u0131 daha da derinle\u015ftirecek ve pratiksel olarak i\u015fin usul\u00fcn\u00fc tam teferruatl\u0131 masaya yat\u0131raca\u011f\u0131z. \u015eimdi \u00f6ncelikle i\u015f kurallar\u0131n\u0131 bar\u0131nd\u0131racak s\u0131n\u0131flar\u0131 olu\u015fturabilmek i\u00e7in ‘PeopleFitForTheJobSpecification’ s\u0131n\u0131f\u0131nda kulland\u0131\u011f\u0131m\u0131z gibi generic olan base Specification<T><\/code> s\u0131n\u0131f\u0131n\u0131 olu\u015fturmam\u0131z gerekmektedir. <\/p>\n
\n\r\nabstract class Specification<T>\r\n{\r\n    public abstract Expression<Func<T, bool>> ToExpression();\r\n    public bool IsSatisfiedBy(T entity)\r\n    {\r\n        Func<T, bool> predicate = ToExpression().Compile();\r\n        return predicate(entity);\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nBu s\u0131n\u0131f domain bilgisi gere\u011fi tan\u0131mlanacak i\u015f kural\u0131n\u0131n uyumlu olup olmad\u0131\u011f\u0131n\u0131 kontrol edebilmek i\u00e7in ‘IsSatisfiedBy’ metodunu bar\u0131nd\u0131rmaktad\u0131r. Bu metot i\u00e7erisinde ‘ToExpression’ isimli abstract olarak tan\u0131mlanm\u0131\u015f metot imzas\u0131 compile edilmekte ve gerekli kontrol bunun \u00fczerinden ger\u00e7ekle\u015ftirilerek uygulamadan encapsulate edilmektedir.<\/p>\n
Bu tan\u0131mlamadan sonra uygulama s\u00fcrecinde kullanaca\u011f\u0131m\u0131z t\u00fcm i\u015f kurallar\u0131n\u0131 yukar\u0131daki ‘PeopleFitForTheJobSpecification’ s\u0131n\u0131f\u0131nda oldu\u011fu gibi \u00f6zel specification s\u0131n\u0131flar\u0131 ile temsil edebiliriz.<\/p>\n
Bir ka\u00e7 \u00f6rnek yaparsak e\u011fer;<\/p>\n
Sadece erkek ki\u015fileri temsil eden specification;<\/p>\n
\n\r\nclass OnlyMenSpecification : Specification<Person>\r\n{\r\n    public override Expression<Func<Person, bool>> ToExpression()\r\n    {\r\n        return p => p.Gender == Gender.Man;\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nSadece kad\u0131n olan ve 18 ya\u015f\u0131ndan b\u00fcy\u00fck olan ki\u015fileri temsil eden specification;<\/p>\n
\n\r\nclass WomenAndOver18YearsOldOnlySpecification : Specification<Person>\r\n{\r\n    public override Expression<Func<Person, bool>> ToExpression()\r\n    {\r\n        return p => p.Gender == Gender.Woman && p.Age > 18;\r\n    }\r\n}\r\n<\/pre>\n<\/div>\n2020’den \u00f6nce \u00fcretilmi\u015f ve 18 ya\u015f\u0131n \u00fczerindeki ki\u015fileri temsil eden specification;<\/p>\n
\n\r\nclass PersonsOver18YearsOfAgeManufacturedBefore2020 : Specification<Person>\r\n{\r\n    public override Expression<Func<Person, bool>> ToExpression()\r\n    {\r\n        return p => p.CreatedDate.Year <= 2020 && p.Age > 18;\r\n    }\r\n}\r\n<\/pre>\n<\/div>\n\u0130\u015fte bu kadar… Olu\u015fturulan bu specification’lar\u0131 isterseniz query yahut validation i\u015flemleri s\u0131ras\u0131nda kullanabilir ve b\u00f6ylece i\u015f kurallar\u0131n\u0131 uygulama \u00e7ap\u0131nda hem anlamsal olarak daha verimli kullanabilir hem de merkezi bir noktadan y\u00f6netilebilir k\u0131labilirsiniz.<\/p>\n
Composite Specification<\/h4>\nOlu\u015fturulan specification’lar\u0131 AND<\/code>, OR<\/code> ve NOT<\/code> gibi mant\u0131ksal operat\u00f6rler e\u015fli\u011finde birle\u015ftirerek kullanmaya Composite Specification<\/em> denmektedir. Bunun i\u00e7in a\u015fa\u011f\u0131daki gibi bu mant\u0131ksal operat\u00f6rlere kar\u015f\u0131l\u0131k \u00f6zel specification s\u0131n\u0131flar\u0131 tan\u0131mlanabilir.<\/p>\n
T\u00fcm s\u0131n\u0131flarda ortak kullan\u0131laca\u011f\u0131 i\u00e7in \u00f6ncelikle a\u015fa\u011f\u0131daki ‘ParameterReplacer’ s\u0131n\u0131f\u0131 tan\u0131mlanmal\u0131d\u0131r;<\/p>\n
\n\r\nclass ParameterReplacer : ExpressionVisitor\r\n{\r\n    private readonly ParameterExpression _parameter;\r\n    public ParameterReplacer(ParameterExpression parameter)\r\n        => _parameter = parameter;\r\n    protected override Expression VisitParameter(ParameterExpression node)\r\n        => base.VisitParameter(_parameter);\r\n}\r\n<\/pre>\n<\/div>\nBurada ParameterExpression<\/code> ile constructor’dan gelen parametre temsil edilmekte ve ‘VisitParameter’ metodu ile bu parametrenin i\u015flevi devreye sokulmaktad\u0131r. Hakl\u0131 olarak neye yarayacak bu hoca la?<\/em><\/strong> diye sordu\u011funuzu duyar gibiyim… Bizler bu parametre ile olu\u015fturaca\u011f\u0131m\u0131z AND<\/code>, OR<\/code> ve NOT<\/code> mant\u0131ksal \u00e7al\u0131\u015fmalar\u0131n\u0131 temsil edecek ve \u00f6nc\u00fcl olan specification’lar\u0131m\u0131z ile birle\u015ftirece\u011fiz.<\/p>\n
\u015eimdi devam edince daha da net anla\u015f\u0131lacakt\u0131r kanaatindeyim. Hi\u00e7 vakit kaybetmeden s\u0131ras\u0131yla operat\u00f6rlere kar\u015f\u0131l\u0131k specification’lar\u0131 in\u015fa edelim.<\/p>\n
And<\/em> i\u00e7in;<\/p>\n
\n\r\nclass AndSpecification<T> : Specification<T>\r\n{\r\n    private readonly Specification<T> _left;\r\n    private readonly Specification<T> _right;\r\n\r\n    public AndSpecification(Specification<T> left, Specification<T> right)\r\n    {\r\n        _left = left;\r\n        _right = right;\r\n    }\r\n\r\n    public override Expression<Func<T, bool>> ToExpression()\r\n    {\r\n        Expression<Func<T, bool>> leftExpression = _left.ToExpression();\r\n        Expression<Func<T, bool>> rightExpression = _right.ToExpression();\r\n\r\n        ParameterExpression parameterExpression = Expression.Parameter(typeof(T));\r\n        BinaryExpression andExpression = Expression.AndAlso(leftExpression.Body, rightExpression.Body);\r\n        andExpression = (BinaryExpression)new ParameterReplacer(parameterExpression).Visit(andExpression);\r\n\r\n        return Expression.Lambda<Func<T, bool>>(andExpression, parameterExpression);\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nOr<\/em> i\u00e7in;<\/p>\n
\n\r\nclass OrSpecification<T> : Specification<T>\r\n{\r\n    private readonly Specification<T> _left;\r\n    private readonly Specification<T> _right;\r\n\r\n    public OrSpecification(Specification<T> left, Specification<T> right)\r\n    {\r\n        _left = left;\r\n        _right = right;\r\n    }\r\n\r\n    public override Expression<Func<T, bool>> ToExpression()\r\n    {\r\n        Expression<Func<T, bool>> leftExpression = _left.ToExpression();\r\n        Expression<Func<T, bool>> rightExpression = _right.ToExpression();\r\n\r\n        ParameterExpression parameterExpression = Expression.Parameter(typeof(T));\r\n        BinaryExpression orExpression = Expression.OrElse(leftExpression.Body, rightExpression.Body);\r\n        orExpression = (BinaryExpression)new ParameterReplacer(parameterExpression).Visit(orExpression);\r\n\r\n        return Expression.Lambda<Func<T, bool>>(orExpression, parameterExpression);\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nNotEqual<\/em> i\u00e7in;<\/p>\n
\n\r\nclass NotEqualSpecification<T> : Specification<T>\r\n{\r\n    private readonly Specification<T> _left;\r\n    private readonly Specification<T> _right;\r\n\r\n    public NotEqualSpecification(Specification<T> left, Specification<T> right)\r\n    {\r\n        _left = left;\r\n        _right = right;\r\n    }\r\n\r\n    public override Expression<Func<T, bool>> ToExpression()\r\n    {\r\n        Expression<Func<T, bool>> leftExpression = _left.ToExpression();\r\n        Expression<Func<T, bool>> rightExpression = _right.ToExpression();\r\n\r\n        ParameterExpression parameterExpression = Expression.Parameter(typeof(T));\r\n\r\n        BinaryExpression notEqualExpression = Expression.NotEqual(leftExpression.Body, rightExpression.Body);\r\n        notEqualExpression = (BinaryExpression)new ParameterReplacer(parameterExpression).Visit(notEqualExpression);\r\n\r\n        return Expression.Lambda<Func<T, bool>>(notEqualExpression, parameterExpression);\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nEqual<\/em> i\u00e7in;<\/p>\n
\n\r\nclass EqualSpecification<T> : Specification<T>\r\n{\r\n    private readonly Specification<T> _left;\r\n    private readonly Specification<T> _right;\r\n\r\n    public EqualSpecification(Specification<T> left, Specification<T> right)\r\n    {\r\n        _left = left;\r\n        _right = right;\r\n    }\r\n\r\n    public override Expression<Func<T, bool>> ToExpression()\r\n    {\r\n        Expression<Func<T, bool>> leftExpression = _left.ToExpression();\r\n        Expression<Func<T, bool>> rightExpression = _right.ToExpression();\r\n\r\n        ParameterExpression parameterExpression = Expression.Parameter(typeof(T));\r\n\r\n        BinaryExpression equalExpression = Expression.Equal(leftExpression.Body, rightExpression.Body);\r\n        equalExpression = (BinaryExpression)new ParameterReplacer(parameterExpression).Visit(equalExpression);\r\n\r\n        return Expression.Lambda<Func<T, bool>>(equalExpression, parameterExpression);\r\n    }\r\n}\r\n<\/pre>\n<\/div>\nMant\u0131ksal operat\u00f6rler i\u00e7in olu\u015fturdu\u011fumuz specification’lara g\u00f6z atarsan\u0131z e\u011fer hepsinde ortak i\u015f olarak, composite bir \u015fekilde ilgili operat\u00f6r ile birle\u015ftirilecek specification’lar sol(_left) ve sa\u011f(_right) olmak \u00fczere temsil edilmekte ve ‘ToExpression’ metodu i\u00e7erisinde de bu specification’lar expression’a d\u00f6n\u00fc\u015ft\u00fcr\u00fclmektedirler. Akabinde her birinde Expression.Parameter<\/code> ile bir parametre olu\u015fturulmakta ve mant\u0131ksal operat\u00f6re g\u00f6re specification’lar davran\u0131\u015fa tabi tutulmakta ve bu davran\u0131\u015f BinaryExpression<\/code> t\u00fcr\u00fcnden elde edilmektedir. Ve son olarak ilk ba\u015fta olu\u015fturdu\u011fumuz ParameterReplacer<\/code> s\u0131n\u0131f\u0131 ile, Expression.Parameter<\/code> komutu e\u015fli\u011finde \u00fcretilen parametreye bu davran\u0131\u015f ‘Visit’ metodu ile ge\u00e7irilmekte ve ‘Lambda’ fonksiyonu ile davran\u0131\u015f i\u015flenmektedir.<\/p>\n
Tabi bu operat\u00f6rlere \u00f6zel \u00e7al\u0131\u015fmalardan sonra a\u015fa\u011f\u0131daki gibi Specification<T><\/code> s\u0131n\u0131f\u0131nda da ilgili operat\u00f6rlere kar\u015f\u0131l\u0131k fonksiyonlar tan\u0131mlanmal\u0131d\u0131r ki her bir specification \u00fczerinden bir sonraki istenilen mant\u0131kta \u00e7a\u011fr\u0131labilsin.<\/p>\n
\n\r\nabstract class Specification<T>\r\n{\r\n    public abstract Expression<Func<T, bool>> ToExpression();\r\n    public bool IsSatisfiedBy(T entity)\r\n    {\r\n        Func<T, bool> predicate = ToExpression().Compile();\r\n        return predicate(entity);\r\n    }\r\n\r\n    public Specification<T> And(Specification<T> specification)\r\n        => new AndSpecification<T>(this, specification);\r\n    public Specification<T> Or(Specification<T> specification)\r\n        => new OrSpecification<T>(this, specification);\r\n    public Specification<T> NotEqual(Specification<T> specification)\r\n        => new NotEqualSpecification<T>(this, specification);\r\n    public Specification<T> Equal(Specification<T> specification)\r\n        => new EqualSpecification<T>(this, specification);\r\n}\r\n<\/pre>\n<\/div>\nArd\u0131ndan ister in-memory’de isterseniz de a\u015fa\u011f\u0131daki gibi IQueryable<\/code> sorgular\u0131nda rahatl\u0131kla kullan\u0131labilmektedir.<\/p>\n
\n\r\nApplicationDbContext context = new();\r\n\r\nWomenAndOver18YearsOldOnlySpecification s1 = new();\r\nPersonsOver18YearsOfAgeManufacturedBefore2020 s2 = new();\r\nPeopleFitForTheJobSpecification s3 = new();\r\nOnlyMenSpecification s4 = new();\r\n\r\nvar query = context.Persons\r\n    .Where(s1.And(s2)\r\n             .Or(s3)\r\n             .And(s4)\r\n             .ToExpression()\r\n          )\r\n    .ToQueryString();\r\nConsole.WriteLine(query);\r\n<\/pre>\n<\/div>\n\u00d6zellikle IQueryable<\/code> sorgular\u0131nda \u00fcretilecek query’leri merak edebilme ihtimalinizden dolay\u0131 yukar\u0131daki \u00f6rnek \u00e7al\u0131\u015fman\u0131n \u00e7\u0131kt\u0131s\u0131na g\u00f6z atmakta fayda vard\u0131r.
\n<\/a><\/p>\n
Nihai olarak;
\nUygulama baz\u0131nda domain bilgileri do\u011frultusunda genel kabul g\u00f6rm\u00fc\u015f i\u015f kurallar\u0131n\u0131 specification pattern ile merkezi bir noktaya ta\u015f\u0131yarak daha y\u00f6netilebilir bir hale getirmenin avantajlar\u0131n\u0131 m\u00fcmk\u00fcn mertebe g\u00f6zlemlemeye \u00e7al\u0131\u015fm\u0131\u015f bulunuyoruz. \u00d6zellikle bu yap\u0131lanman\u0131n, IQueryable<\/code> sorgular\u0131n\u0131 repository s\u0131n\u0131flar\u0131 \u00fczerinden daha esnek bir \u015fekilde \u00fcretebilmemizi sa\u011flayacak bir olgunluk getirdi\u011fine dair sizlerin de kanaati vard\u0131r diye d\u00fc\u015f\u00fcn\u00fcyorum.<\/p>\n
\u0130lgilenenlerin faydalanmas\u0131 dile\u011fiyle…
\nSonraki yaz\u0131lar\u0131mda g\u00f6r\u00fc\u015fmek \u00fczere…
\n\u0130yi \u00e7al\u0131\u015fmalar…<\/p>\n
Not : Specification Pattern’a dair ve \u00f6zellikle Composite Specification i\u00e7in yapm\u0131\u015f oldu\u011fumuz \u00f6rnek \u00e7al\u0131\u015fmay\u0131 a\u015fa\u011f\u0131daki github adresinden inceleyebilirsiniz.
\nhttps:\/\/github.com\/gncyyldz\/Specification_Pattern_Example<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
Merhaba, Bu i\u00e7eri\u011fimizde, domain i\u00e7erisinde i\u015f kurallar\u0131n\u0131 kaps\u00fclleyerek kod taban\u0131nda farkl\u0131 noktalarda yeniden kullan\u0131labilir k\u0131lmam\u0131z\u0131 ve b\u00f6ylece bu kurallar\u0131 tek bir yerden merkezi olarak y\u00f6netmemizi sa\u011flayan Specification modelini ele alacak ve detayl\u0131 bir \u015fekilde...<\/p>\n","protected":false},"author":1,"featured_media":25905,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[153],"tags":[4726,750,4725],"class_list":["post-25885","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-design-pattern","tag-composite-specification","tag-design-pattern","tag-specification-pattern"],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25885","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/comments?post=25885"}],"version-history":[{"count":17,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25885\/revisions"}],"predecessor-version":[{"id":25906,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/posts\/25885\/revisions\/25906"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media\/25905"}],"wp:attachment":[{"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/media?parent=25885"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/categories?post=25885"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.gencayyildiz.com\/blog\/wp-json\/wp\/v2\/tags?post=25885"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}