{"id":31042,"date":"2025-10-05T02:31:26","date_gmt":"2025-10-04T23:31:26","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/strongresult-ile-ilk-nuget-paketinizi-yayimlama-rehberi\/"},"modified":"2025-10-05T02:31:26","modified_gmt":"2025-10-04T23:31:26","slug":"strongresult-ile-ilk-nuget-paketinizi-yayimlama-rehberi","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/strongresult-ile-ilk-nuget-paketinizi-yayimlama-rehberi\/","title":{"rendered":"StrongResult ile \u0130lk NuGet Paketinizi Yay\u0131mlama Rehberi"},"content":{"rendered":"

<\/p>\n

C# uygulamalar\u0131n\u0131zda hata y\u00f6netimi karma\u015f\u0131k ve okunmaz hale mi geliyor? Belki de try-catch<\/code> bloklar\u0131n\u0131n katmanlar\u0131 aras\u0131nda bo\u011fuluyor, kodunuzun i\u015f mant\u0131\u011f\u0131n\u0131 g\u00f6rmekte zorlan\u0131yorsunuz. \u0130\u015fte bu noktada, sonu\u00e7 odakl\u0131 programlama (result-oriented programming) imdad\u0131n\u0131za yeti\u015fiyor ve kodunuzu daha temiz, anla\u015f\u0131l\u0131r ve g\u00fcvenli hale getiriyor. Bu makalede, bir hafta sonu \u00f6\u011frenim projesi olarak geli\u015ftirdi\u011fim StrongResult<\/strong> ad\u0131nda basit bir NuGet paketi olu\u015fturma ve yay\u0131mlama s\u00fcrecimi ad\u0131m ad\u0131m sizlerle payla\u015faca\u011f\u0131m. B\u00f6ylece hem hata y\u00f6netiminde yeni bir perspektif kazanacak hem de kendi NuGet paketinizi nas\u0131l olu\u015fturup t\u00fcm geli\u015ftirici toplulu\u011fuyla payla\u015faca\u011f\u0131n\u0131z\u0131 \u00f6\u011freneceksiniz.<\/p>\n

Modern yaz\u0131l\u0131m geli\u015ftirme s\u00fcre\u00e7lerinde, uygulamalar\u0131m\u0131z\u0131n g\u00fcvenilirli\u011fi ve hatas\u0131z \u00e7al\u0131\u015fmas\u0131 kritik \u00f6neme sahiptir. Geleneksel olarak, C# dilinde hatalar\u0131 y\u00f6netmek i\u00e7in istisnalar\u0131 (exceptions) kullan\u0131r\u0131z. try-catch<\/code> bloklar\u0131, bir i\u015flem s\u0131ras\u0131nda beklenmedik bir durum olu\u015ftu\u011funda program ak\u0131\u015f\u0131n\u0131 keserek hata durumunu yakalamam\u0131z\u0131 sa\u011flar. Ancak, bu yakla\u015f\u0131m\u0131n baz\u0131 dezavantajlar\u0131 bulunmaktad\u0131r. \u00d6zellikle i\u015f mant\u0131\u011f\u0131 hatalar\u0131 veya beklenen ba\u015far\u0131s\u0131z durumlar i\u00e7in istisnalar\u0131 kullanmak, kod okunabilirli\u011fini d\u00fc\u015f\u00fcrebilir ve performans \u00fczerinde olumsuz etkiler yaratabilir. \u00d6rne\u011fin, bir API iste\u011fi s\u0131ras\u0131nda ba\u011flant\u0131 hatas\u0131 veya ge\u00e7ersiz giri\u015f gibi durumlar, program\u0131n tamamen \u00e7\u00f6kmesine neden olacak “istisna”lardan ziyade, i\u015flem sonucunun bir par\u00e7as\u0131 olarak ele al\u0131nmal\u0131d\u0131r.<\/p>\n

\u0130stisnalar, genellikle “ola\u011fan\u00fcst\u00fc durumlar” i\u00e7in tasarlanm\u0131\u015ft\u0131r. Veritaban\u0131 ba\u011flant\u0131s\u0131n\u0131n aniden kesilmesi, disk alan\u0131n\u0131n dolmas\u0131 gibi beklenmedik olaylar istisna f\u0131rlatmay\u0131 hak eder. Ancak, kullan\u0131c\u0131dan al\u0131nan verinin ge\u00e7erli olmamas\u0131 veya bir kayd\u0131n veritaban\u0131nda bulunamamas\u0131 gibi durumlar, i\u015f ak\u0131\u015f\u0131n\u0131n do\u011fal bir par\u00e7as\u0131 olarak de\u011ferlendirilebilir. Bu gibi durumlarda istisna f\u0131rlatmak ve yakalamak, asl\u0131nda bir kontrol ak\u0131\u015f\u0131 mekanizmas\u0131 olarak kullan\u0131ld\u0131\u011f\u0131nda kodun karma\u015f\u0131kl\u0131\u011f\u0131n\u0131 art\u0131r\u0131r ve beklenmedik durumlarla, beklenen ba\u015far\u0131s\u0131z durumlar\u0131 ay\u0131rt etmeyi zorla\u015ft\u0131r\u0131r. \u0130\u015fte bu noktada, sonu\u00e7 odakl\u0131 programlama (Result-Oriented Programming) devreye girer. Bu yakla\u015f\u0131m, bir i\u015flemin sonucunu, ba\u015far\u0131 veya ba\u015far\u0131s\u0131zl\u0131k durumunu ve ilgili verileri a\u00e7\u0131k\u00e7a ifade eden bir t\u00fcr olarak temsil etmeyi \u00f6nerir. Bu sayede, fonksiyon imzalar\u0131, olas\u0131 sonu\u00e7lar\u0131 net bir \u015fekilde belirtir ve \u00e7a\u011f\u0131ran kodun bu durumlar\u0131 zarif bir \u015fekilde ele almas\u0131n\u0131 kolayla\u015ft\u0131r\u0131r. StrongResult da tam olarak bu felsefeyi benimseyen, basit ama etkili bir yard\u0131mc\u0131 pakettir.<\/p>\n

StrongResult Nedir ve Hata Y\u00f6netimini Nas\u0131l Kolayla\u015ft\u0131r\u0131r?<\/h2>\nStrongResult, bir i\u015flemin sonucunu Success<\/code> (ba\u015far\u0131l\u0131) veya Failure<\/code> (ba\u015far\u0131s\u0131z) olarak ifade etmenizi sa\u011flayan basit bir yap\u0131 sunar. Geleneksel try-catch<\/code> mekanizmas\u0131n\u0131n aksine, StrongResult, ba\u015far\u0131l\u0131 bir i\u015flemin de\u011ferini veya ba\u015far\u0131s\u0131z bir i\u015flemin hata detaylar\u0131n\u0131 tip g\u00fcvenli bir \u015fekilde ta\u015f\u0131yan jenerik bir Result<\/code> veya Result<\/code> yap\u0131s\u0131 sa\u011flar. Buradaki T<\/code>, i\u015flemin ba\u015far\u0131l\u0131 olmas\u0131 durumunda d\u00f6nd\u00fcr\u00fclecek veri tipini, E<\/code> ise ba\u015far\u0131s\u0131zl\u0131k durumunda d\u00f6nd\u00fcr\u00fclecek hata tipini temsil eder. Bu sayede, fonksiyonunuzun imzas\u0131, olas\u0131 t\u00fcm sonu\u00e7lar\u0131 a\u00e7\u0131k\u00e7a belirtir ve \u00e7a\u011fr\u0131 yapan kodun bu durumlar\u0131 ele almas\u0131 gerekti\u011fini garanti eder.<\/p>\n
Peki, bu yakla\u015f\u0131m hata y\u00f6netimini nas\u0131l kolayla\u015ft\u0131r\u0131r? \u00d6ncelikle, fonksiyon imzalar\u0131 daha a\u00e7\u0131klay\u0131c\u0131 hale gelir. Bir metodun Result<\/code> d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fc g\u00f6rd\u00fc\u011f\u00fcn\u00fczde, bu metodun ya bir User<\/code> nesnesiyle ba\u015far\u0131l\u0131 olaca\u011f\u0131n\u0131 ya da bir Error<\/code> nesnesiyle ba\u015far\u0131s\u0131z olaca\u011f\u0131n\u0131 hemen anlars\u0131n\u0131z. Bu, metodun yan etkilerini veya olas\u0131 sonu\u00e7lar\u0131n\u0131 tahmin etmeye \u00e7al\u0131\u015fmak yerine, do\u011frudan ne bekleyece\u011finizi bilmenizi sa\u011flar. \u0130kinci olarak, Result<\/code> nesnesi \u00fczerinde IsSuccess<\/code> veya IsFailure<\/code> gibi \u00f6zellikler veya Match<\/code> gibi metodlar kullanarak, ba\u015far\u0131l\u0131 ve ba\u015far\u0131s\u0131z durumlar\u0131 ayr\u0131\u015ft\u0131r\u0131lm\u0131\u015f bir \u015fekilde ele alabilirsiniz. Bu, ko\u015fullu dallanmalar\u0131 daha okunur hale getirir ve hata durumlar\u0131n\u0131 atlaman\u0131z\u0131 engeller.<\/p>\n
\u00dc\u00e7\u00fcnc\u00fc olarak, Result<\/code> nesneleri genellikle bir zincirleme (chaining) mekanizmas\u0131 sunar. \u00d6rne\u011fin, bir Bind<\/code> veya Map<\/code> metodu kullanarak, bir i\u015flemin ba\u015far\u0131l\u0131 sonucunu al\u0131p bir sonraki i\u015fleme aktarabilirsiniz. E\u011fer ara i\u015flemlerden biri ba\u015far\u0131s\u0131z olursa, zincir kesilir ve hata nesnesi do\u011frudan sonuca ta\u015f\u0131n\u0131r. Bu, i\u00e7 i\u00e7e if<\/code> veya try-catch<\/code> bloklar\u0131ndan ka\u00e7\u0131narak daha ak\u0131c\u0131 ve i\u015flevsel bir kod yazman\u0131z\u0131 sa\u011flar. StrongResult, \u00f6zellikle mikroservis mimarileri veya karma\u015f\u0131k i\u015f ak\u0131\u015flar\u0131 olan uygulamalarda, hata propogasyonunu (hata yay\u0131l\u0131m\u0131n\u0131) standart ve anla\u015f\u0131l\u0131r bir hale getirerek geli\u015ftiricilerin i\u015fini b\u00fcy\u00fck \u00f6l\u00e7\u00fcde kolayla\u015ft\u0131r\u0131r. Kodunuzun her yerinde tutarl\u0131 bir hata y\u00f6netimi stratejisi izlemenize olanak tan\u0131r, bu da daha az s\u00fcrprizle ve daha g\u00fcvenilir uygulamalarla sonu\u00e7lan\u0131r.<\/p>\n
Uzman \u0130pucu: Sonu\u00e7 odakl\u0131 programlama, \u00f6zellikle Functional Programming paradigmalar\u0131yla yak\u0131ndan ili\u015fkilidir. Bu yakla\u015f\u0131m, yan etkileri (side effects) azaltma ve fonksiyonlar\u0131 daha saf hale getirme prensibini destekler, bu da test edilebilirli\u011fi ve kod kalitesini art\u0131r\u0131r.<\/aside>\nKendi StrongResult Paketinizi Nas\u0131l Olu\u015fturursunuz? Ad\u0131m Ad\u0131m Rehber<\/h2>\nKendi NuGet paketinizi olu\u015fturman\u0131n ilk ad\u0131m\u0131, paketin temel i\u015flevselli\u011fini sa\u011flayacak kodu yazmakt\u0131r. StrongResult i\u00e7in bu, Result<\/code> yap\u0131s\u0131n\u0131 ve yard\u0131mc\u0131 metodlar\u0131n\u0131 tan\u0131mlamak anlam\u0131na geliyor. Bu b\u00f6l\u00fcmde, basit bir Result<\/code> s\u0131n\u0131f\u0131n\u0131 nas\u0131l tasarlayaca\u011f\u0131m\u0131z\u0131 ve temel \u00f6zelliklerini nas\u0131l uygulayaca\u011f\u0131m\u0131z\u0131 g\u00f6rece\u011fiz.<\/p>\n
1. Yeni Bir Class Library Projesi Olu\u015fturmak<\/h3>\n\u00d6ncelikle, Visual Studio’da veya .NET CLI kullanarak yeni bir Class Library projesi olu\u015fturun. Bu proje, NuGet paketinizin \u00e7ekirde\u011fini olu\u015fturacakt\u0131r.<\/p>\n
\ndotnet new classlib -n StrongResult\ncd StrongResult\n    <\/pre>\n<\/code><\/p>\n
2. Temel Result S\u0131n\u0131f\u0131n\u0131 Tasarlamak<\/h3>\nBasitlik ad\u0131na, StrongResult'\u0131 Result<\/code> ve Result<\/code> olmak \u00fczere iki ana jenerik yap\u0131 olarak tasarlayabiliriz. \u0130lk ad\u0131m olarak, sadece ba\u015far\u0131l\u0131 veya ba\u015far\u0131s\u0131z durumu belirten jenerik olmayan bir Result<\/code> ve ard\u0131ndan de\u011fer ta\u015f\u0131yan Result<\/code> yap\u0131s\u0131n\u0131 olu\u015ftural\u0131m. Hatalar\u0131 temsil etmek i\u00e7in ise basit bir Error<\/code> s\u0131n\u0131f\u0131 tan\u0131mlayabiliriz.<\/p>\n
\n\/\/ StrongResult\/Error.cs\nnamespace StrongResult\n{\n    public class Error\n    {\n        public string Code { get; }\n        public string Message { get; }\n        public Dictionary Metadata { get; }\n\n        private Error(string code, string message, Dictionary metadata = null)\n        {\n            Code = code;\n            Message = message;\n            Metadata = metadata ?? new Dictionary();\n        }\n\n        public static Error Validation(string message, string code = \"ValidationError\")\n            => new Error(code, message);\n        public static Error NotFound(string message, string code = \"NotFoundError\")\n            => new Error(code, message);\n        public static Error Unauthorized(string message, string code = \"UnauthorizedError\")\n            => new Error(code, message);\n        public static Error Unexpected(string message = \"An unexpected error occurred.\", string code = \"UnexpectedError\")\n            => new Error(code, message);\n\n        public override string ToString() => $\"{Code}: {Message}\";\n    }\n}\n\n\/\/ StrongResult\/Result.cs (Non-generic base for easier pattern matching\/utility)\nnamespace StrongResult\n{\n    public abstract class Result\n    {\n        public bool IsSuccess { get; }\n        public bool IsFailure => !IsSuccess;\n        public Error Error { get; }\n\n        protected Result(bool isSuccess, Error error)\n        {\n            IsSuccess = isSuccess;\n            Error = error; \/\/ Should be null if IsSuccess is true\n        }\n\n        \/\/ Static factory methods for convenience\n        public static Result Success(TValue value) => new SuccessResult(value);\n        public static Result Success(TValue value) where TError : Error => new SuccessResult(value);\n        public static Result Failure(Error error) => new FailureResult(error);\n        public static Result Failure(TError error) where TError : Error => new FailureResult(error);\n    }\n\n    public abstract class Result : Result\n    {\n        public TValue Value { get; }\n\n        protected Result(TValue value, bool isSuccess, Error error) : base(isSuccess, error)\n        {\n            Value = value; \/\/ Default or actual value\n        }\n\n        public TValue GetValueOrDefault(TValue defaultValue = default)\n        {\n            return IsSuccess ? Value : defaultValue;\n        }\n\n        \/\/ Implicit conversions for convenience\n        public static implicit operator Result(TValue value) => Result.Success(value);\n        public static implicit operator Result(Error error) => Result.Failure(error);\n    }\n\n    public class SuccessResult : Result\n    {\n        public SuccessResult(TValue value) : base(value, true, null) { }\n    }\n\n    public class FailureResult : Result\n    {\n        public FailureResult(Error error) : base(default, false, error)\n        {\n            if (error == null)\n                throw new ArgumentNullException(nameof(error), \"Error cannot be null for a failure result.\");\n        }\n    }\n}\n    <\/pre>\n<\/code><\/p>\n
Bu temel yap\u0131lar sayesinde, fonksiyonlar\u0131m\u0131z art\u0131k sadece bir de\u011fer d\u00f6nd\u00fcrmek yerine, i\u015flemin ba\u015far\u0131l\u0131 m\u0131 yoksa ba\u015far\u0131s\u0131z m\u0131 oldu\u011funu a\u00e7\u0131k\u00e7a belirten bir Result<\/code> nesnesi d\u00f6nd\u00fcrebilecek. Bu, \u00e7a\u011fr\u0131 yapan kodun hata durumlar\u0131n\u0131 if<\/code> bloklar\u0131 veya switch<\/code> ifadeleriyle kolayca ele almas\u0131n\u0131 sa\u011flar. \u00d6zellikle implicit operator<\/code> tan\u0131mlar\u0131, ba\u015far\u0131l\u0131 bir de\u011fer veya bir hata nesnesi d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fczde, bunlar\u0131n otomatik olarak bir Result<\/code> nesnesine d\u00f6n\u00fc\u015ft\u00fcr\u00fclmesini sa\u011flayarak kod yaz\u0131m\u0131n\u0131 basitle\u015ftirir.<\/p>\n
3. StrongResult ile Ak\u0131c\u0131 Kod Yazmak: Map ve Bind Metotlar\u0131<\/h3>\nStrongResult'\u0131n g\u00fcc\u00fc, sadece ba\u015far\u0131l\u0131\/ba\u015far\u0131s\u0131z durumlar\u0131n\u0131 ta\u015f\u0131makta de\u011fil, ayn\u0131 zamanda bu durumlar \u00fczerinde ak\u0131c\u0131 i\u015flemler yapabilme yetene\u011finde yatar. Map<\/code> ve Bind<\/code> (veya Then<\/code>) metodlar\u0131, bu ak\u0131\u015fkanl\u0131\u011f\u0131 sa\u011flayan temel yap\u0131 ta\u015flar\u0131d\u0131r. Bu metodlar, i\u015flevsel programlama prensiplerinden ilham alarak, bir Result<\/code> nesnesi \u00fczerindeki d\u00f6n\u00fc\u015f\u00fcmleri ve zincirleme i\u015flemleri basitle\u015ftirir.<\/p>\n
Map Metodu:<\/strong> Map<\/code> metodu, ba\u015far\u0131l\u0131 bir Result<\/code> nesnesinin i\u00e7indeki de\u011feri ba\u015fka bir tipe d\u00f6n\u00fc\u015ft\u00fcrmek istedi\u011finizde kullan\u0131l\u0131r. E\u011fer Result<\/code> ba\u015far\u0131s\u0131z durumdaysa, Map<\/code> hi\u00e7bir i\u015flem yapmadan orijinal hata nesnesini koruyarak yeni bir ba\u015far\u0131s\u0131z Result<\/code> d\u00f6nd\u00fcr\u00fcr. Bu, bir Result<\/code>'i Result<\/code>'e d\u00f6n\u00fc\u015ft\u00fcrmek gibi senaryolarda olduk\u00e7a kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n
\n\/\/ Result.cs i\u00e7ine ekleyin\npublic Result Map(Func mapper)\n{\n    return IsSuccess\n        ? Result.Success(mapper(Value))\n        : Result.Failure(Error);\n}\n    <\/pre>\n<\/code><\/p>\n
Bind Metodu:<\/strong> Bind<\/code> metodu ise daha g\u00fc\u00e7l\u00fc bir ara\u00e7t\u0131r. Bir Result<\/code> nesnesinin i\u00e7indeki de\u011feri, kendisi de bir Result<\/code> d\u00f6nd\u00fcren ba\u015fka bir fonksiyona ge\u00e7irmek istedi\u011finizde kullan\u0131l\u0131r. Yani, ba\u015far\u0131l\u0131 bir i\u015flem sonucunu al\u0131p, bu sonucun \u00fczerine ba\u015fka bir potansiyel olarak ba\u015far\u0131s\u0131z olabilecek i\u015flemi zincirlemek i\u00e7in idealdir. E\u011fer mevcut Result<\/code> ba\u015far\u0131s\u0131zsa, Bind<\/code> hi\u00e7bir i\u015flem yapmadan do\u011frudan hata nesnesini ta\u015f\u0131yan yeni bir ba\u015far\u0131s\u0131z Result<\/code> d\u00f6nd\u00fcr\u00fcr. Bu, bir dizi i\u015flemi birbiri ard\u0131na s\u0131ralarken, herhangi bir noktadaki hatan\u0131n t\u00fcm zinciri kesmesini ve hemen hata durumunu d\u00f6nd\u00fcrmesini sa\u011flar.<\/p>\n
\n\/\/ Result.cs i\u00e7ine ekleyin\npublic Result Bind(Func> binder)\n{\n    return IsSuccess\n        ? binder(Value)\n        : Result.Failure(Error);\n}\n\n\/\/ Ayr\u0131ca asenkron versiyonlar\u0131 da ekleyebiliriz (Task tabanl\u0131):\npublic async Task> BindAsync(Func>> binder)\n{\n    return IsSuccess\n        ? await binder(Value)\n        : Result.Failure(Error);\n}\n\npublic async Task> MapAsync(Func> mapper)\n{\n    return IsSuccess\n        ? Result.Success(await mapper(Value))\n        : Result.Failure(Error);\n}\n    <\/pre>\n<\/code><\/p>\n
Bu metodlarla, karma\u015f\u0131k i\u015f ak\u0131\u015flar\u0131n\u0131 daha okunabilir ve y\u00f6netilebilir bir \u015fekilde yazabilirsiniz. \u00d6rne\u011fin, bir kullan\u0131c\u0131n\u0131n kayd\u0131n\u0131 olu\u015fturup, ard\u0131ndan ona bir ho\u015f geldin e-postas\u0131 g\u00f6nderme i\u015flemini zincirleme olarak ele alal\u0131m:<\/p>\n
\npublic class UserService\n{\n    public Result CreateUser(string email, string password)\n    {\n        if (string.IsNullOrWhiteSpace(email))\n            return Error.Validation(\"Email cannot be empty.\");\n        \/\/ ... user creation logic ...\n        return new User { Email = email, Id = Guid.NewGuid() };\n    }\n\n    public Result SendWelcomeEmail(User user)\n    {\n        if (user == null)\n            return Error.Unexpected(\"User cannot be null for welcome email.\");\n        \/\/ ... email sending logic ...\n        return true; \/\/ Email sent successfully\n    }\n\n    public Result RegisterUserAndSendWelcomeEmail(string email, string password)\n    {\n        return CreateUser(email, password)\n            .Bind(user => SendWelcomeEmail(user)); \/\/ E\u011fer CreateUser ba\u015far\u0131l\u0131 olursa SendWelcomeEmail \u00e7a\u011fr\u0131l\u0131r\n    }\n}\n\n\/\/ Kullan\u0131m \u00f6rne\u011fi\nvar userService = new UserService();\nvar registrationResult = userService.RegisterUserAndSendWelcomeEmail(\"test@example.com\", \"password123\");\n\nif (registrationResult.IsSuccess)\n{\n    Console.WriteLine(\"Kullan\u0131c\u0131 ba\u015far\u0131yla kaydedildi ve ho\u015f geldin e-postas\u0131 g\u00f6nderildi!\");\n}\nelse\n{\n    Console.WriteLine($\"Kay\u0131t ba\u015far\u0131s\u0131z oldu: {registrationResult.Error}\");\n}\n    <\/pre>\n<\/code><\/p>\n
Bu \u00f6rnekte, CreateUser<\/code> metodundan d\u00f6nen Result<\/code> nesnesi, Bind<\/code> metodu arac\u0131l\u0131\u011f\u0131yla SendWelcomeEmail<\/code> metoduna aktar\u0131l\u0131r. E\u011fer CreateUser<\/code> herhangi bir nedenle ba\u015far\u0131s\u0131z olursa (\u00f6rne\u011fin email ge\u00e7ersizse), Bind<\/code> metodu SendWelcomeEmail<\/code>'i hi\u00e7 \u00e7a\u011f\u0131rmadan do\u011frudan CreateUser<\/code>'\u0131n hata sonucunu d\u00f6nd\u00fcrecektir. Bu, hata y\u00f6netimini \u00e7ok daha ak\u0131c\u0131 ve kontrol edilebilir hale getirir.<\/p>\n
Bir NuGet Paketi Nas\u0131l Yay\u0131mlan\u0131r? Ad\u0131m Ad\u0131m K\u0131lavuz<\/h2>\nKodunuzu StrongResult olarak haz\u0131rlad\u0131ktan sonra, s\u0131ra geldi bu kodu bir NuGet paketi olarak paketlemeye ve yay\u0131mlamaya. Bu s\u00fcre\u00e7, projenizi t\u00fcm .NET geli\u015ftiricileriyle payla\u015fman\u0131z\u0131 sa\u011flar. \u0130\u015fte ad\u0131m ad\u0131m nas\u0131l yapaca\u011f\u0131n\u0131z:<\/p>\n
1. Proje Dosyas\u0131n\u0131 (.csproj<\/code>) NuGet \u0130\u00e7in Yap\u0131land\u0131rmak<\/h3>\n\u0130lk olarak, Class Library projenizin .csproj<\/code> dosyas\u0131n\u0131 d\u00fczenleyerek NuGet paketi i\u00e7in gerekli meta verileri eklemeniz gerekir. Bu meta veriler, paketinizi NuGet Gallery'de tan\u0131mlayacak ve kullan\u0131c\u0131lar\u0131n paketinizi kolayca bulmas\u0131n\u0131 sa\u011flayacakt\u0131r.<\/p>\n
\n\n\n  \n    net8.0<\/TargetFramework>\n    enable<\/ImplicitUsings>\n    enable<\/Nullable>\n\n    true<\/IsPackable> \n    StrongResult<\/PackageId> \n    1.0.0<\/Version> \n    Ad\u0131n\u0131z Soyad\u0131n\u0131z<\/Authors> \n    \u015eirketiniz (iste\u011fe ba\u011fl\u0131)<\/Company>\n    C# uygulamalar\u0131 i\u00e7in sonu\u00e7 odakl\u0131, tip g\u00fcvenli hata y\u00f6netimi sa\u011flayan hafif bir k\u00fct\u00fcphane.<\/Description> \n    https:\/\/github.com\/kullaniciadiniz\/StrongResult<\/RepositoryUrl> \n    https:\/\/github.com\/kullaniciadiniz\/StrongResult<\/PackageProjectUrl> \n    result, error-handling, functional, csharp, nuget, strongresult<\/PackageTags> \n    MIT<\/PackageLicenseExpression> \n    true<\/GeneratePackageOnBuild> \n  <\/PropertyGroup>\n\n<\/Project>\n    <\/pre>\n<\/code><\/p>\n
Bu \u00f6zellikler, paketinizi NuGet Gallery'de daha bulunabilir ve profesyonel hale getirecektir. \u00d6zellikle PackageId<\/code>'nin benzersiz oldu\u011fundan emin olun.<\/p>\n
2. NuGet Paketinizi Olu\u015fturmak (.nupkg)<\/h3>\nProje dosyan\u0131z\u0131 yap\u0131land\u0131rd\u0131ktan sonra, paketi olu\u015fturmak olduk\u00e7a basittir. Projenizin k\u00f6k dizininde a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n
\ndotnet pack --configuration Release\n    <\/pre>\n<\/code><\/p>\n
Bu komut, bin\/Release<\/code> klas\u00f6r\u00fc alt\u0131nda StrongResult.1.0.0.nupkg<\/code> gibi bir dosya olu\u015fturacakt\u0131r. Bu dosya, t\u00fcm paketlenmi\u015f kodunuzu, meta verilerinizi ve ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131z\u0131 i\u00e7erir.<\/p>\n
3. NuGet.org API Anahtar\u0131 Almak<\/h3>\nPaketinizi nuget.org'a yay\u0131mlamak i\u00e7in bir nuget.org hesab\u0131n\u0131z\u0131n olmas\u0131 ve bir API anahtar\u0131 olu\u015fturman\u0131z gerekir. nuget.org'a giri\u015f yapt\u0131ktan sonra, sa\u011f \u00fcstteki kullan\u0131c\u0131 ad\u0131n\u0131za t\u0131klayarak \"API Keys\" b\u00f6l\u00fcm\u00fcne gidin ve yeni bir anahtar olu\u015fturun. Bu anahtar\u0131 g\u00fcvende tutun, \u00e7\u00fcnk\u00fc paketinizi yay\u0131mlamak i\u00e7in gerekli olacakt\u0131r.<\/p>\n
NuGet.org API Anahtar\u0131 Olu\u015fturma Sayfas\u0131<\/figcaption><\/p>\n(Bu bir g\u00f6rsel betimlemesidir, ger\u00e7ek bir g\u00f6rsel de\u011fildir. NuGet.org sitesinde, API Anahtarlar\u0131 b\u00f6l\u00fcm\u00fcnde yeni bir anahtar olu\u015fturma formu bulunur. Anahtar\u0131n s\u00fcresini ve hangi paketler \u00fczerinde i\u015flem yapabilece\u011fini belirleyebilirsiniz.)<\/em><\/p>\n<\/figure>\n
4. NuGet Paketini Yay\u0131mlamak<\/h3>\nSon ad\u0131m, olu\u015fturdu\u011funuz .nupkg<\/code> dosyas\u0131n\u0131 nuget.org'a g\u00f6ndermektir. API anahtar\u0131n\u0131z\u0131 kullanarak a\u015fa\u011f\u0131daki komutu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n
\ndotnet nuget push \"bin\/Release\/StrongResult.1.0.0.nupkg\" --api-key  --source https:\/\/api.nuget.org\/v3\/index.json\n    <\/pre>\n<\/code><\/p>\n
<\/code> k\u0131sm\u0131n\u0131 kendi API anahtar\u0131n\u0131zla de\u011fi\u015ftirin. Komut ba\u015far\u0131l\u0131 olursa, paketinizi nuget.org'da g\u00f6rebilirsiniz. \u0130lk yay\u0131mlama biraz zaman alabilir (genellikle birka\u00e7 dakika), ancak daha sonra g\u00fcncellemeler daha h\u0131zl\u0131 yay\u0131mlanacakt\u0131r.<\/p>\n
Bu s\u00fcre\u00e7, kendi yaratt\u0131\u011f\u0131n\u0131z kodu geni\u015f bir geli\u015ftirici toplulu\u011fuyla payla\u015fman\u0131z\u0131 sa\u011flar. StrongResult gibi bir yard\u0131mc\u0131 k\u00fct\u00fcphane, sizin veya ekibinizin hata y\u00f6netimini standartla\u015ft\u0131rmas\u0131na ve kod kalitesini art\u0131rmas\u0131na yard\u0131mc\u0131 olabilir.<\/p>\n
Ger\u00e7ek D\u00fcnya Senaryosu: Bir E-ticaret Uygulamas\u0131nda Sipari\u015f Y\u00f6netimi<\/h2>\nStrongResult'\u0131n ger\u00e7ek bir uygulamada nas\u0131l fark yaratabilece\u011fini daha iyi anlamak i\u00e7in, bir e-ticaret uygulamas\u0131ndaki sipari\u015f olu\u015fturma s\u00fcrecini inceleyelim. Bu s\u00fcre\u00e7, genellikle birden fazla ad\u0131mdan ve olas\u0131 hata durumundan olu\u015fur:<\/p>\n
\nKullan\u0131c\u0131 sepetindeki \u00fcr\u00fcnlerin ge\u00e7erlili\u011fini kontrol etme.<\/li>\n
Kullan\u0131c\u0131n\u0131n bakiyesini veya \u00f6deme y\u00f6ntemini do\u011frulama.<\/li>\n
Sipari\u015fi veritaban\u0131na kaydetme.<\/li>\n
Stoklar\u0131 g\u00fcncelleme.<\/li>\n
Kullan\u0131c\u0131ya sipari\u015f onay e-postas\u0131 g\u00f6nderme.<\/li>\n<\/ol>\nGeleneksel try-catch<\/code> yakla\u015f\u0131m\u0131yla bu i\u015flemlerin her birinde olu\u015fabilecek hatalar\u0131 y\u00f6netmek, i\u00e7 i\u00e7e try-catch<\/code> bloklar\u0131na veya erken return<\/code> ifadeleriyle dolu karma\u015f\u0131k bir koda yol a\u00e7abilir. Ancak StrongResult ile bu s\u00fcre\u00e7 \u00e7ok daha ak\u0131c\u0131 ve okunabilir hale gelir.<\/p>\n
Senaryo Uygulamas\u0131<\/h3>\nA\u015fa\u011f\u0131daki \u00f6rnek kod, StrongResult kullanarak bu ad\u0131mlar\u0131 nas\u0131l zincirleyebilece\u011finizi g\u00f6stermektedir. Her metod, ba\u015far\u0131l\u0131 bir durumda bir Result<\/code> veya hata durumunda bir Error<\/code> d\u00f6nd\u00fcr\u00fcr.<\/p>\n
\nusing StrongResult;\nusing System;\nusing System.Threading.Tasks;\n\npublic class Order\n{\n    public Guid Id { get; set; }\n    public Guid UserId { get; set; }\n    public decimal TotalAmount { get; set; }\n    public List ProductSkus { get; set; }\n}\n\npublic class OrderCreationRequest\n{\n    public Guid UserId { get; set; }\n    public List ProductSkus { get; set; }\n    public decimal PaymentAmount { get; set; }\n}\n\npublic class ECommerceService\n{\n    \/\/ 1. \u00dcr\u00fcnlerin ge\u00e7erlili\u011fini kontrol etme\n    public Result> ValidateProducts(List productSkus)\n    {\n        if (productSkus == null || !productSkus.Any())\n            return Error.Validation(\"Sipari\u015f sepeti bo\u015f olamaz.\");\n\n        \/\/ \u00d6rnek: \u00dcr\u00fcnlerin varl\u0131\u011f\u0131n\u0131 ve stok durumunu kontrol et\n        foreach (var sku in productSkus)\n        {\n            if (sku == \"INVALID_SKU\") \/\/ Varsay\u0131msal hata durumu\n                return Error.NotFound($\"'{sku}' koduyla \u00fcr\u00fcn bulunamad\u0131.\");\n            \/\/ Ger\u00e7ek d\u00fcnyada DB'den veya ba\u015fka bir servisten kontrol edilir\n        }\n        return productSkus;\n    }\n\n    \/\/ 2. \u00d6deme y\u00f6ntemini do\u011frulama\n    public Result ProcessPayment(Guid userId, decimal amount)\n    {\n        if (amount <= 0)\n            return Error.Validation(\"\u00d6deme miktar\u0131 s\u0131f\u0131rdan b\u00fcy\u00fck olmal\u0131d\u0131r.\");\n\n        \/\/ \u00d6rnek: Kullan\u0131c\u0131n\u0131n bakiyesi yetersiz veya \u00f6deme servisi hatas\u0131\n        if (userId == Guid.Parse(\"f00dbeef-f00d-f00d-f00d-f00dbeef0001\")) \/\/ Varsay\u0131msal yetersiz bakiye kullan\u0131c\u0131s\u0131\n            return Error.Unauthorized(\"Yetersiz bakiye.\");\n\n        \/\/ Ger\u00e7ek d\u00fcnyada bir \u00f6deme gateway'i ile entegrasyon\n        Console.WriteLine($\"Kullan\u0131c\u0131 {userId} i\u00e7in {amount} TL \u00f6deme ba\u015far\u0131yla i\u015flendi.\");\n        return true;\n    }\n\n    \/\/ 3. Sipari\u015fi veritaban\u0131na kaydetme\n    public Result SaveOrder(Guid userId, List productSkus, decimal totalAmount)\n    {\n        var newOrder = new Order\n        {\n            Id = Guid.NewGuid(),\n            UserId = userId,\n            ProductSkus = productSkus,\n            TotalAmount = totalAmount\n        };\n        \/\/ Ger\u00e7ek d\u00fcnyada DB kayd\u0131 yap\u0131l\u0131r\n        Console.WriteLine($\"Sipari\u015f {newOrder.Id} ba\u015far\u0131yla veritaban\u0131na kaydedildi.\");\n        return newOrder;\n    }\n\n    \/\/ 4. Stoklar\u0131 g\u00fcncelleme (asenkron olabilir)\n    public async Task> UpdateStockAsync(List productSkus)\n    {\n        await Task.Delay(100); \/\/ Varsay\u0131msal asenkron i\u015flem\n        foreach (var sku in productSkus)\n        {\n            if (sku == \"OUT_OF_STOCK_SKU\") \/\/ Varsay\u0131msal stok hatas\u0131\n                return Error.Unexpected($\"'{sku}' \u00fcr\u00fcn\u00fcn\u00fcn sto\u011fu g\u00fcncellenemedi.\");\n        }\n        Console.WriteLine(\"Stoklar ba\u015far\u0131yla g\u00fcncellendi.\");\n        return true;\n    }\n\n    \/\/ 5. Sipari\u015f onay e-postas\u0131 g\u00f6nderme\n    public async Task> SendOrderConfirmationEmailAsync(Order order)\n    {\n        await Task.Delay(50); \/\/ Varsay\u0131msal asenkron i\u015flem\n        if (order.UserId == Guid.Parse(\"f00dbeef-f00d-f00d-f00d-f00dbeef0002\")) \/\/ Varsay\u0131msal email g\u00f6nderim hatas\u0131\n            return Error.Unexpected(\"Sipari\u015f onay e-postas\u0131 g\u00f6nderilemedi.\");\n        Console.WriteLine($\"Sipari\u015f {order.Id} i\u00e7in onay e-postas\u0131 g\u00f6nderildi.\");\n        return true;\n    }\n\n    \/\/ T\u00fcm sipari\u015f s\u00fcrecini zincirleme\n    public async Task> CreateOrderAsync(OrderCreationRequest request)\n    {\n        return await Task.FromResult(ValidateProducts(request.ProductSkus))\n            .Bind(validatedSkus => ProcessPayment(request.UserId, request.PaymentAmount)\n                .Map(_ => validatedSkus)) \/\/ \u00d6deme ba\u015far\u0131l\u0131ysa validatedSkus'u bir sonraki ad\u0131ma ge\u00e7ir\n            .Bind(async validatedSkus => await SaveOrder(request.UserId, validatedSkus, request.PaymentAmount)\n                .Bind(async order => await UpdateStockAsync(order.ProductSkus)\n                    .Map(_ => order))) \/\/ Stok g\u00fcncellenirse order'\u0131 bir sonraki ad\u0131ma ge\u00e7ir\n            .Bind(async order => await SendOrderConfirmationEmailAsync(order)\n                .Map(_ => order)); \/\/ E-posta g\u00f6nderilirse order'\u0131 geri d\u00f6nd\u00fcr\n    }\n}\n\n\/\/ Uygulama giri\u015fi (Program.cs)\n\/\/ var service = new ECommerceService();\n\/\/ var request = new OrderCreationRequest\n\/\/ {\n\/\/     UserId = Guid.NewGuid(),\n\/\/     ProductSkus = new List { \"PRODUCT_A\", \"PRODUCT_B\" },\n\/\/     PaymentAmount = 150.00m\n\/\/ };\n\n\/\/ var result = await service.CreateOrderAsync(request);\n\n\/\/ if (result.IsSuccess)\n\/\/ {\n\/\/     Console.WriteLine($\"Sipari\u015f ba\u015far\u0131yla olu\u015fturuldu: {result.Value.Id}\");\n\/\/ }\n\/\/ else\n\/\/ {\n\/\/     Console.Error.WriteLine($\"Sipari\u015f olu\u015fturulamad\u0131: {result.Error}\");\n\/\/ }\n    <\/pre>\n<\/code><\/p>\n
Yukar\u0131daki \u00f6rnekte, her bir i\u015flem bir Result<\/code> d\u00f6nd\u00fcrd\u00fc\u011f\u00fc i\u00e7in, Bind<\/code> ve Map<\/code> metodlar\u0131n\u0131 kullanarak t\u00fcm s\u00fcreci tek bir ak\u0131c\u0131 zincirde birle\u015ftirebiliyoruz. E\u011fer zincirdeki herhangi bir ad\u0131m ba\u015far\u0131s\u0131z olursa, zincir otomatik olarak kesilir ve hata, en son Result<\/code> nesnesine ta\u015f\u0131n\u0131r. Bu sayede, kodunuzda karma\u015f\u0131k if\/else<\/code> merdivenlerinden veya i\u00e7 i\u00e7e try-catch<\/code> bloklar\u0131ndan kurtulursunuz. Hata y\u00f6netimi merkezi ve belirgin hale gelir, bu da kodun hem okunabilirli\u011fini hem de bak\u0131m\u0131n\u0131 b\u00fcy\u00fck \u00f6l\u00e7\u00fcde art\u0131r\u0131r. Ayr\u0131ca, BindAsync<\/code> ve MapAsync<\/code> sayesinde asenkron i\u015flemleri de bu ak\u0131\u015fa dahil etmek olduk\u00e7a kolayd\u0131r. Bu, \u00f6zellikle modern, I\/O yo\u011fun uygulamalar i\u00e7in paha bi\u00e7ilmez bir avantaj sa\u011flar.<\/p>\n
Geli\u015fmi\u015f StrongResult Kullan\u0131m\u0131 ve \u0130pu\u00e7lar\u0131<\/h2>\nStrongResult gibi bir k\u00fct\u00fcphane, temel hata y\u00f6netiminin \u00f6tesinde, daha karma\u015f\u0131k senaryolarda da etkili bir \u015fekilde kullan\u0131labilir. Deneyimli geli\u015ftiriciler i\u00e7in bu b\u00f6l\u00fcmde baz\u0131 ileri d\u00fczey ipu\u00e7lar\u0131 ve p\u00fcf noktalar\u0131 payla\u015faca\u011f\u0131m.<\/p>\n
1. \u00d6zel Hata Tipleri Olu\u015fturma<\/h3>\nStrongResult'\u0131n Error<\/code> s\u0131n\u0131f\u0131 basit bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r, ancak i\u015f uygulamalar\u0131nda genellikle daha spesifik hata tiplerine ihtiya\u00e7 duyulur. \u00d6rne\u011fin, \"Ge\u00e7ersiz Kullan\u0131c\u0131 Ad\u0131\", \"\u00dcr\u00fcn Stokta Yok\" veya \"\u00d6deme Ba\u015far\u0131s\u0131z\" gibi farkl\u0131 hata senaryolar\u0131n\u0131 ay\u0131rt etmek isteyebilirsiniz. StrongResult'\u0131 jenerik Result<\/code> olarak geni\u015fleterek, kendi \u00f6zel hata s\u0131n\u0131flar\u0131n\u0131z\u0131 kullanabilirsiniz.<\/p>\n
\n\/\/ StrongResult\/CustomError.cs\nnamespace MyProject.Errors\n{\n    public abstract class AppError : StrongResult.Error\n    {\n        protected AppError(string code, string message, Dictionary metadata = null)\n            : base(code, message, metadata) { }\n    }\n\n    public class UserNotFoundError : AppError\n    {\n        public UserNotFoundError(Guid userId)\n            : base(\"UserNotFound\", $\"Kullan\u0131c\u0131 ID '{userId}' bulunamad\u0131.\", new Dictionary { { \"UserId\", userId } }) { }\n    }\n\n    public class PaymentFailedError : AppError\n    {\n        public PaymentFailedError(string reason)\n            : base(\"PaymentFailed\", $\"\u00d6deme ba\u015far\u0131s\u0131z: {reason}\", new Dictionary { { \"Reason\", reason } }) { }\n    }\n}\n\n\/\/ Kullan\u0131m \u00f6rne\u011fi:\n\/\/ public Result GetUser(Guid userId)\n\/\/ {\n\/\/     \/\/ ... user bulma mant\u0131\u011f\u0131 ...\n\/\/     if (user == null)\n\/\/         return new UserNotFoundError(userId);\n\/\/     return user;\n\/\/ }\n    <\/pre>\n<\/code><\/p>\n
Bu, hatan\u0131n tipine g\u00f6re daha hassas kontrol ak\u0131\u015flar\u0131 yazman\u0131za olanak tan\u0131r ve hatan\u0131n ne anlama geldi\u011fini daha a\u00e7\u0131k\u00e7a belirtir.<\/p>\n
2. Asenkron \u0130\u015flemlerle Birlikte Kullan\u0131m<\/h3>\n.NET d\u00fcnyas\u0131nda asenkron programlama (async\/await<\/code>) yayg\u0131n olarak kullan\u0131lmaktad\u0131r. StrongResult'\u0131n BindAsync<\/code> ve MapAsync<\/code> metodlar\u0131, asenkron i\u015flemleri sonu\u00e7 zincirine dahil etmeyi kolayla\u015ft\u0131r\u0131r. B\u00f6ylece, I\/O yo\u011fun uygulamalarda bile temiz ve okunabilir bir hata y\u00f6netimi sa\u011flayabilirsiniz. Yukar\u0131daki ger\u00e7ek d\u00fcnya senaryosunda bu kullan\u0131ma \u00f6rnek verilmi\u015ftir. Ancak daha genel bir kullan\u0131m\u0131 a\u015fa\u011f\u0131da g\u00f6rebilirsiniz:<\/p>\n
\npublic class DataService\n{\n    public async Task> FetchDataAsync(int id)\n    {\n        await Task.Delay(100); \/\/ Simulate network call\n        if (id <= 0)\n            return Error.Validation(\"ID ge\u00e7erli de\u011fil.\");\n        if (id == 99)\n            return Error.NotFound(\"Veri bulunamad\u0131.\");\n        return $\"Veri: {id}\";\n    }\n\n    public async Task> ProcessAndParseDataAsync(string data)\n    {\n        await Task.Delay(50); \/\/ Simulate CPU-bound work\n        if (!int.TryParse(data.Split(':')[1].Trim(), out int parsedValue))\n            return Error.Unexpected(\"Veri ayr\u0131\u015ft\u0131r\u0131lamad\u0131.\");\n        return parsedValue * 2;\n    }\n\n    public async Task> GetDataAndProcess(int inputId)\n    {\n        return await FetchDataAsync(inputId)\n            .BindAsync(async data => await ProcessAndParseDataAsync(data));\n    }\n}\n    <\/pre>\n<\/code><\/p>\n
Bu \u00f6rnek, iki asenkron i\u015flemi nas\u0131l BindAsync<\/code> ile zincirleyebilece\u011finizi g\u00f6sterir. \u0130lk i\u015flem ba\u015far\u0131s\u0131z olursa, ikincisi hi\u00e7 \u00e7al\u0131\u015ft\u0131r\u0131lmaz.<\/p>\n
3. StrongResult'\u0131 Dependency Injection (DI) ile Entegre Etme<\/h3>\nStrongResult'\u0131n kendisi temel bir k\u00fct\u00fcphane oldu\u011fundan, do\u011frudan DI ile entegre edilecek bir servisi yoktur. Ancak, Result<\/code> nesneleri d\u00f6nd\u00fcren servislerinizi DI kapsay\u0131c\u0131s\u0131na kaydederken, StrongResult'\u0131 verimli bir \u015fekilde kullanabilirsiniz. \u00d6rne\u011fin, t\u00fcm \"Application Service\" katman\u0131n\u0131z Result<\/code> d\u00f6nd\u00fcr\u00fcyorsa, bu servisleri DI arac\u0131l\u0131\u011f\u0131yla kolayca y\u00f6netebilirsiniz. Bu, uygulama genelinde tutarl\u0131 bir desen olu\u015fturman\u0131za yard\u0131mc\u0131 olur.<\/p>\n
4. Performans ve Optimizasyon<\/h3>\nStrongResult kullanmak, genellikle istisnalar\u0131 yakalamaktan daha performansl\u0131d\u0131r, \u00e7\u00fcnk\u00fc istisna f\u0131rlatma ve yakalama i\u015flemleri pahal\u0131d\u0131r. Ancak, her zaman oldu\u011fu gibi, a\u015f\u0131r\u0131 nesne olu\u015fturmaktan ka\u00e7\u0131nmak \u00f6nemlidir. Result<\/code> s\u0131n\u0131flar\u0131n\u0131z\u0131n hafif oldu\u011fundan ve gereksiz bellek tahsisinden ka\u00e7\u0131nd\u0131\u011f\u0131ndan emin olun. struct<\/code> tabanl\u0131 Result<\/code> uygulamalar\u0131, daha fazla performans isteyen senaryolarda de\u011ferlendirilebilir. Yine de, \u00e7o\u011fu i\u015f uygulamas\u0131 i\u00e7in class<\/code> tabanl\u0131 bir uygulama yeterli olacakt\u0131r.<\/p>\n
StrongResult'\u0131n bu geli\u015fmi\u015f kullan\u0131mlar\u0131, uygulaman\u0131z\u0131n daha sa\u011flam, esnek ve s\u00fcrd\u00fcr\u00fclebilir olmas\u0131na yard\u0131mc\u0131 olabilir. Hata y\u00f6netimini kodunuzun merkezine alarak, hem geli\u015ftirici deneyimini hem de kullan\u0131c\u0131 deneyimini \u00f6nemli \u00f6l\u00e7\u00fcde iyile\u015ftirebilirsiniz.<\/p>\n