Signals-pubsub 1.1.0

There is a newer version of this package available.
See the version list below for details.
dotnet add package Signals-pubsub --version 1.1.0                
NuGet\Install-Package Signals-pubsub -Version 1.1.0                
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="Signals-pubsub" Version="1.1.0" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Signals-pubsub --version 1.1.0                
#r "nuget: Signals-pubsub, 1.1.0"                
#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 Signals-pubsub as a Cake Addin
#addin nuget:?package=Signals-pubsub&version=1.1.0

// Install Signals-pubsub as a Cake Tool
#tool nuget:?package=Signals-pubsub&version=1.1.0                

Signals

Signals is a simple to use pub-sub/workflow hybrid framework.

It is designed to allow you to separate concerns and call workflows in an async manner

Installation

Use Nuget to install the latest version

Install-Package Signals-pubsub

Usage

Setting up

(in startup.cs)

using Signals.Extensions;

public void ConfigureServices(IServiceCollection services)
{
    // add controllers etc
    services.AddSignalProcessor(); // add an instance of ISignalProcessor
    services.AddSignalHandlers(GetType().Assembly); // adds any signal handlers from this assembly
}

make a message class to send, derived from the Signal class

using Signals;

public class BookDetailSignal : Signal
{
    public BookDetailSignal(int bookId)
    {
        BookId = bookId;
    }

    public int BookId { get; }
    public Book BookDetails { get; set; }

}

Making a call

Add some handler classes to process the signal

using Signals.Context;
using Signals.Handlers;

public class BookDetailsHandler : SignalHandler<BookDetailSignal>
{
    public override int Order => 0; // this denotes the order of handlers (lowest first)
    
    protected override Task OnSignal(BookPriceSignal signal, ISignalContext context, CancellationToken token)
    {
        var bookDetails = dataRepository.GetBook(signal.BookId);
        signal.BookDetails = bookDetails;            
        return Task.CompletedTask;
    }

    // this is called if this OR any later handlers throw an exception
    protected override Task OnSignalAbort(BookPriceSignal signal, ISignalContext context, CancellationToken token)
    {
        Console.WriteLine($"An error was thrown {context.Exception.Message}");
        return Task.CompletedTask;
    }
}

public class BookDetailsLoggerHandler : SignalHandler<BookDetailSignal>
{
    public override int Order => 1; // this denotes the order of handlers (lowest first)
    protected override Task OnSignal(BookPriceSignal signal, ISignalContext context, CancellationToken token)
    {
        if(signal.BookDetails == null)
        {
            Console.WriteLine($"book details not found {BookDetailSignal.Id}");
        } 
        else
        {
            Console.WriteLine($"book details found {BookDetailSignal.Id}");
    
        }           
        return Task.CompletedTask;
    }
}

// Pipeline handlers recieve EVERY signal sent 
public class LoggingPipelineHandler : PipelineHandler
{
        
    public override Task ProcessStart(ISignal signal, CancellationToken token)
    {
        Console.WriteLine("signal processing started");
        return Task.CompletedTask;
    }

    public override Task ProcessEnd(ISignal signal, CancellationToken token)
    {
        Console.WriteLine("signal processing ended");        
        return Task.CompletedTask;
    }
}

You can send a message (from a controller in this case)

public class HomeController : Controller
{
        private readonly ISignalProcessor signalProcessor;

        public HomeController(ISignalProcessor signalProcessor)
        {  
            // inject a version of ISignalProcessor , called signalProcessor           
            this.signalProcessor = signalProcessor;
        }

        public async Task<IActionResult> Detail(int id)
        {
            // we can send a signal to get the book details from a workflow
            var signal = await signalProcessor.Process(new BookDetailSignal(id));
            return View(signal.BookDetails);
        }

        public async Task<IActionResult> WorkFlows()
        {
            // we can see what workflows have been set up 
            var workFlow = signalProcessor.WorkFlows;
            return View(workFlow);
        }
}

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

MIT

Product Compatible and additional computed target framework versions.
.NET net5.0 is compatible.  net5.0-windows was computed.  net6.0 was computed.  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.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
1.3.0 446 5/5/2022
1.2.0 309 12/8/2021
1.1.0 268 12/7/2021
1.0.0 620 12/6/2021