11 packages returned for Tags:"success"

Outcome.NET uses generics and a fluent interface to add metadata to your return value. It's a very expressive, clean result wrapper.

return result by form of "{success : bool, message : string ,data : object}"

Outcome.NET uses generics and a fluent interface to add metadata to your return value. It's a very expressive, clean result wrapper. Outcome really shines when you're orchestrating complex logic, because the fluent interface makes it easy to roll up messages from multiple methods, and even from... More information

Source code package. A utility class for running external processes in various ways, with timeout and success/failure notification and getting their output recorded via a logger.

Api.Result is a basic package created to encapsulate, standardize and facilitate the return of results with messages, errors or data for communication between server to server, server to client or between application layers such as ASP.NET Core Web API.

Provides two lite-weight classes that can be used to check the success or failure of operations returned from methods.

A super lightweight handy utility to return a result with a value on success or errors on failure. Better error handling.

A simple, strongly typed and boilerplate poor implementation of the Result pattern.

Provides a re-factoring and re-imagining of the Code Fixes elements deployed in the default Analysis and Code Fixes project template. This particular assembly focuses on Code Fixes only as part of that re-factoring effort.

Provides a set of general purpose Fluent Assertion extension methods methods extending from Xunit.

Provides a re-factoring and re-imagining of the Code Fixes elements deployed in the default Analysis and Code Fixes project template. This particular assembly focuses on Code Fixes only as part of that re-factoring effort.