This extension method is quite complex and is frustrating
when a unit test passes-through it. That's because extension
methods can't be mocked in tests.
The triggers-for-activity-blueprint functionality
is quite complex just on its own, so I have moved this to
a new service.
Once again the integration test which is left behind proves
that it still does the same job.
* Activity picker dialog
* Activity picker
* Activity editor
* Activity property fields
* Blazor bindings for Elsa designer
* Only index triggers from published & enabled workflow definitions
* Handle case of null workflow blueprint not found
* Add check for zero duration and general scheduler exceptions
* Don't rethrow expression evaluation failure
* Workflow definition settings editor modal
* Integration between stencil and blazor 🎉
* Fix expression type conversion
* Add publish button and restructure components
* Fix up workflow definition ID vs workflow definition version ID
* Update EF Core migrations
* Fix Workflow Publisher
* Fix version display
* Add Import menu item
* Initial version of workflow reviver
* Fix DI things
* Rename workflow builder parameter to `builder`
* Update EF Core stores to use short-lived db contexts
* Update serializer to use new settings to reset ID seed
* Write fault details
* Add faulty workflows sample project
* Switch to free & open source Z.EntityFramework.Plus.EFCore
* Add content type header
* Fix call to virtual OnSaving/OnLoading
* Fix retry
Before this change, the aforementioned activities would always schedule the Done outcome.
After this change, the Done outcome is scheduled **after** the Iterate branch and True or False branches have completed
* Incremental work on workflow message queuing
* Add extension to register message consumers
* Update Rebus logging to use Microsoft Extensions Logging
* Synchronize quartz job and run instance consumer with distributed locking
* Add service bus options
* Adding Activities, Workflows, TriggerProviders and WorkflowContextProviders by Reflection
* Activities stored in ElsaOptions, instead of IServiceCollection
* Remove the empty XML comments
* Renamed ElsaConfigurationsOptions to ElsaConfiguration
* Small enhancements
* Workflows stored in ElsaOptions, instead of IServiceCollection
* Instantiated workflows can now be added
* Workflow instance was not registered to DI
* Add Elsa.Activities.Rebus project to solution
Co-authored-by: Sipke Schoorstra <sipkeschoorstra@outlook.com>
