Tags: rbnswartz/elsa-core
Tags
Replace TaskExecutingServer with StartupRunnerHostedService (elsa-wor… …kflows#237) This solves an issue where the Dashboard site would not be able to run in IIS, due to an IIS filter that expects a IISServer instance, while it was being decorated with a custom type. Fortunately, as of .NET Core 3, background hosted services now execute before the server starts, which makes them perfect for async initialization.
Fixed yaml serialisation and updated to YamlDotNet (elsa-workflows#236) * Fixed Yaml serialisation/deserialisation Copied json serializer settings from JsonTokenFormatter, apart from CamelCasePropertyNamesContractResolver, as the yaml already had the correct case, and this would cause activity state (which has PascalCasing) to be camelCased too * Updated YamlDotNet.Standard to YamlDotNet Switched package as YamlDotNet.Standard has been unlisted on Nuget
Fix issue due to parallel access to DbContext Fixes elsa-workflows#219
Fix object disposed bug (elsa-workflows#116) * Refactor buggy SignalRequestHandler For some reason, the following code is problematic: await DecryptToken() .BindAsync(GetWorkflowInstanceAsync) .BindAsync(CheckIfExecutingAsync) .MapAsync(ResumeWorkflowAsync); Basically, any lambda in the BindAsync and MapAsync could execute even after the containing method returned * Implement better message handler registration without adding multiple IMediator services * Abstracted Mediator service registration methods. * Add Liquid support for JObject.
PreviousNext