excepticon-dotnet
FluentResults
| excepticon-dotnet | FluentResults | |
|---|---|---|
| - | 10 | |
| 2 | 1,654 | |
| - | - | |
| 0.0 | 0.0 | |
| over 1 year ago | 5 months ago | |
| C# | C# | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
excepticon-dotnet
We haven't tracked posts mentioning excepticon-dotnet yet.
Tracking mentions began in Dec 2020.
FluentResults
-
The Monad Invasion - Part 1: What's a Monad?
FluentResults
-
FluentResults: Simplificando el Manejo de Resultados y Errores en Aplicaciones .NET
altmann/FluentResults: A generalised Result object implementation for .NET/C# (github.com)
-
TypeScript Is Surprisingly OK for Compilers
Or maybe just start using Results as return type and get ValueOrDefault :) But when it comes to handling exceptions, I think it explodes there with ifs and processing IENumerables: https://github.com/altmann/FluentResults
But then again, simpler Results wrapper may be used perhaps. But it is a different way of coding and takes some mental shift on how to think about errors and distinguish between error results and true exceptions.
https://github.com/altmann/FluentResults
-
Exception handling between controller and service
Yep, it's called result pattern, aforementioned above. There was two highlighted implementations - OneOf, FluentResults.
-
Communication - library for Results
What does this library do better or differently than something like Fluent Results?
-
Why is using Exceptions is controversial in low level languages (like C++) but not in C#?
For C# particular - this project https://github.com/altmann/FluentResults
-
Knowledge of generics: isn't it pretty common?
For example https://github.com/altmann/FluentResults is excellent if you want generic results
-
The Operation Result Pattern
It's worth noting that there's also a library called FluentResults as an alternative to this one.
-
Introducing Cranks.Result
Interesting... I just found out that your first intention was to improve FluentResults but your PR got rejected which is a pity. PR: https://github.com/altmann/FluentResults/pull/80. I guess I will have a look at your library in hopes of removing some boilerplate code. Thanks!
What are some alternatives?
Exceptionless - Exceptionless clients for the .NET platform
Result - A result abstraction that can be mapped to HTTP response codes if needed.
EntityFramework.Exceptions - Handle database errors easily when working with Entity Framework Core. Supports SQLServer, PostgreSQL, SQLite, Oracle and MySql.
Cranks.Result - A simple, strongly typed and boilerplate poor implementation of the Result pattern.
Ben.Demystifier - High performance understanding for stack traces (Make error logs more productive)
tweetinvi - Tweetinvi, an intuitive Twitter C# library for the REST and Stream API. It supports .NET, .NETCore, UAP (Xamarin)...
Exceptionless - Exceptionless application
sendgrid-csharp - The Official Twilio SendGrid C#, .NetStandard, .NetCore API Library
ApiExceptions - Reinventing C# exceptions
CSharpFunctionalExtensions - Functional extensions for C#
spectre.console - A .NET library that makes it easier to create beautiful console applications.
error-or - A simple, fluent discriminated union of an error or a result.