Mediator.Net | simple mediator for .Net for sending command | Microservice library

by mayuanyang C# Version: 4.7.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | Mediator.Net Summary

Mediator.Net is a C# library typically used in Architecture, Microservice applications. Mediator.Net has no vulnerabilities, it has a Permissive License and it has low support. However Mediator.Net has 18 bugs. You can download it from GitHub.

A mediator project for .NET.

Support

Quality

Security

License

Reuse

Support

Mediator.Net has a low active ecosystem.

It has 340 star(s) with 48 fork(s). There are 21 watchers for this library.

It had no major release in the last 12 months.

There are 5 open issues and 13 have been closed. On average issues are closed in 45 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Mediator.Net is 4.7.0

Quality

Mediator.Net has 18 bugs (0 blocker, 0 critical, 12 major, 6 minor) and 0 code smells.

Security

Mediator.Net has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Mediator.Net code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Mediator.Net is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

Mediator.Net releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Mediator.Net saves you 3001 person hours of effort in developing the same functionality from scratch.

It has 6472 lines of code, 0 functions and 288 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Mediator.Net

Get all kandi verified functions for this library.

Mediator.Net Key Features

No Key Features are available at this moment for Mediator.Net.

Mediator.Net Examples and Code Snippets

No Code Snippets are available at this moment for Mediator.Net.

Community Discussions

Trending Discussions on Mediator.Net

Can Mediator.Net support multi event handlers as well as inheritance?

QUESTION

Can Mediator.Net support multi event handlers as well as inheritance?

Asked 2017-May-15 at 03:39

can mediator.net support multi event handlers? i want to have multiple handlers listen to the same event and do different thing.

...

ANSWER

Answered 2017-May-15 at 03:39

In Mediator.Net, you can have as many event handlers as you want as long as the message implement the IEvent interface, but only 1 command handler. From your code example, as SimpleCommand is a ICommand which mean that you can only have one handler for it.

In terms of inheritance, ICommand handler need to be the exact type which mean no inheritance is supported. For IEvent, as long as the Handler is assignable from the message type then it should get called, so inheritace is in.

Source https://stackoverflow.com/questions/43929318

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Mediator.Net

Install the nuget package Mediator.Net.
The most powerful thing for the pipelines above is you can add as many middlewares as you want. Follow the following steps to setup a middlewaree. You might need some dependencies in your middleware, there are two ways to do it. Here is a sample middleware.
Add a static class for your middleware
Add a public static extension method in that class you just added, usually follow the UseXxxx naming convention
Add another class for your middleware's specification, note that this is the implementation of your middleware
Pass them in explicitly
Let the IoC container to resolve it for you (if you are using IoC)

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: