SignalFlow 1.0.0.1

dotnet add package SignalFlow --version 1.0.0.1
NuGet\Install-Package SignalFlow -Version 1.0.0.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="SignalFlow" Version="1.0.0.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add SignalFlow --version 1.0.0.1
#r "nuget: SignalFlow, 1.0.0.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install SignalFlow as a Cake Addin
#addin nuget:?package=SignalFlow&version=1.0.0.1

// Install SignalFlow as a Cake Tool
#tool nuget:?package=SignalFlow&version=1.0.0.1

SignalFlow

Last Version : 1.0.0 Last Commit : April 2024 License

Introduction

The SignalFlow repository is an implementation of an event bus for managing and distributing events within an application. It provides functionality for subscribing to and unsubscribing from events, as well as firing events and registering new event signals.

Table of Contents

<a id="installation"/> Installation

<a id="installcli"/> Using .NET CLI

To install the SignalFlow NuGet package using the .NET CLI, open the command-line interface and execute the following command:

dotnet add package SignalFlow --version 1.0.0

<a id="installnugetpackage"/> Using NuGet Package Manager Console

If you prefer using the NuGet Package Manager Console, you can execute the following command:

Install-Package SignalFlow -Version 1.0.0

<a id="installmsbuild"/> Using PackageReference (MSBuild)

For projects that use MSBuild and PackageReference format, you can add the following line to your project file:

<PackageReference Include="SignalFlow" Version="1.0.0" />

<a id="usage"/> Usage

<a id="registering"/> Registering and Unregistering Event Signals

Registering

You can register new event signals dynamically using the RegisterSignal<TSignal> method. This method takes a type parameter TSignal, which represents the event signal to be registered.

var bus = new EventBus();
bus.Register<ExampleSignal>();

After registering an event signal, you can subscribe, unsubscribe, and fire events using that signal.

Unregistering

To unregister an event signal, use the UnRegister<TSignal> method. This method removes the specified event signal type TSignal from the list of registered event signals.

var bus = new EventBus();
bus.UnRegister<ExampleSignal>();

In this example, ExampleSignal is unregistered from the EventBus instance bus. The UnRegister<TSignal> method is useful for dynamically managing the set of event signals that the EventBus instance is configured to handle.

<a id="subscribing"/> Subscribing to Events

<a id="subscribingsync"/> Subscribing To Synchronous Events

To subscribe to an event, you can use the Subscribe<TSignal> method. This method takes a type parameter TSignal, which represents the event signal you want to subscribe to. The event signal should be a class or interface that defines the structure of the event.

bus.Subscribe<ExampleSignal>(HandleEvent);

The HandleMyEvent method is the event handler that will be called when the event is fired. It should have a compatible signature with the event signal.

<a id="subscribingasync"/> Subscribing to Asynchronous Signals

To subscribe to an asynchronous signal, you can use the Subscribe<TSignal> method in the following format:

bus.Subscribe<ExampleSignal>(HandleEventAsync);
// where Method Is
private async Task HandleEventAsync(ExampleSignal signal)
{
    await Task.Delay(5000);
    Console.WriteLine(signal.Id);
}

Here, TestSubscribe is an asynchronous method that returns a Task. It should have a compatible signature with the event signal TestSignal.

<a id="unsubscribing"/> Unsubscribing from Events

Please note that unsubscribing from signals is crucial. To do this, implement the IDisposable interface and unsubscribe from all the signals to which the object is subscribed in its Dispose method.

public class BarReceiver : IDisposable
{
    private readonly IBus _bus;

    public BarReceiver(IBus bus)
    {
        _bus = bus;

        _bus.Subscribe<Examples.ExampleSignal>(HandleEvent);
    }

    private void HandleEvent(Examples.ExampleSignal signal) =>
        Console.WriteLine(signal.Id);

    public void Dispose()
    {
        _bus.UnSubscribe<Examples.ExampleSignal>(HandleEvent);
    }
}

// OR if Async Signal

public class BarReceiver : IDisposable
{
    private readonly IBus _bus;

    public BarReceiver(IBus bus)
    {
        _bus = bus;

        _bus.Subscribe<Examples.ExampleSignal>(HandleEvent);
    }

    private async Task HandleEvent(Examples.ExampleSignal signal)
    {
        // Some Async Code
        await Task.Delay(2000);
        
        Console.WriteLine(signal.Id);
    }
        

    public void Dispose()
    {
        _bus.UnSubscribe<Examples.ExampleSignal>(HandleEvent);
    }
}

To unsubscribe from an event, you can use the UnSubscribe<TSignal> method. This method takes the same type parameter TSignal as the Subscribe method.

bus.UnSubscribe<Examples.ExampleSignal>(HandleEvent);

<a id="firing"/> Firing Events

To fire an event, you can use the Fire<TSignal> method. This method takes a type parameter TSignal, representing the event signal to be fired.

bus.Fire<ExampleSignal>();
// Or, use TryFire if you do not want to receive an exception in case it occurs.
// Please note that if an exception occurs and you are not in Debug Mode, you will not be able to know about it.
bus.TryFire<ExampleSignal>();

All the event handlers that have subscribed to the specified event signal will be called.

<a id="firingwitharguments"/> Firing Events with Arguments

To fire an event with arguments, you can use the Fire<TSignal> or TryFire<TSignal> method variants that accept a Func<TSignal> parameter. This function should return an instance of the event signal with the desired argument values.

bus.Fire(() => new ExampleSignal() { Id = 10 });
// Or, use TryFire if you do not want to receive an exception in case it occurs.
bus.TryFire(() => new ExampleSignal() { Id = 10 });

<a id="asyncfiring"/> Async Firing

To fire an asynchronous signal, you can use the FireAsync method. It can accept an instance of the event signal TSignal or no arguments. The method returns a Task that represents the asynchronous operation.

await _bus.FireAsync<Examples.ExampleSignal>();

You can also pass an instance of the event signal as a parameter:

await _bus.FireAsync<Examples.ExampleSignal>(() => new Examples.ExampleSignal()
{
    Id = 10
});
// If you dont want awaiting signal

<a id="examples"/> Examples

Here are some examples of how you can use the EventBus:

// Subscribe to an event
bus.Subscribe<ExampleSignal>(HandleEvent);

// Unsubscribe from an event
bus.UnSubscribe<ExampleSignal>(HandleEvent);

// Register a new event signal
bus.Register<ExampleSignal>();

// Fire an event
bus.Fire(() => new ExampleSignal() { Id = 10 });
// Or
bus.TryFire(() => new ExampleSignal() { Id = 10 });

In the above example, MyClass subscribes to the TestSignal event with the asynchronous method TestSubscribe. When the event is fired, TestSubscribe is invoked asynchronously to handle the event. Remember to implement the IDisposable interface if you need to unsubscribe from signals when the object is disposed to avoid memory leaks. That's it! You can now leverage the power of asynchronous signals in the EventBus repository to handle events asynchronously in your application.

<a id="contributing"/> Contributing

Contributions to the EventBus repository are welcome! If you find any issues or have suggestions for improvements, please open an issue or submit a pull request on the GitHub repository.

Product Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.
  • net6.0

    • No dependencies.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on SignalFlow:

Package Downloads
SignalFlow.Microsoft.Extensions.DependencyInjection

SignalFlow.Microsoft.Extensions.DependencyInjection is a NuGet package that simplifies the integration of the SignalFlow library with Microsoft.Extensions.DependencyInjection in .NET applications. This package enables seamless dependency injection of SignalFlow services, allowing you to efficiently manage and dispatch signals (events) within your application.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.0.0.1 93 4/6/2024
1.0.0 121 4/6/2024