4f90cfbbdf
* fix: register built-in activation strategy serialization aliases 3.8 type-resolution hardening no longer falls back to Type.GetType, so Studio-selected and 3.7-era SQN activation strategy types failed to deserialize. Register the four built-in strategies with legacy names and advertise registry aliases from the descriptor endpoint. Fixes https://github.com/elsa-workflows/elsa-core/issues/8049 Co-authored-by: Sipke Schoorstra <sipkeschoorstra@outlook.com> * test: DRY activation strategy serialization test setup Extract shared registry/JSON arrange helpers so activation alias tests share setup without collapsing their assertions. Co-authored-by: Sipke Schoorstra <sipkeschoorstra@outlook.com> * test: qualify Options.Create in serialization test helpers Avoid Elsa.Options colliding with Microsoft.Extensions.Options.Options. Co-authored-by: Sipke Schoorstra <sipkeschoorstra@outlook.com> * test: keep activation alias setup local and obvious Drop the shared Testing.Shared helper and extra Runtime wrapper. Those hid one-line registry construction. Leave same-class helpers only. Co-authored-by: Sipke Schoorstra <sipkeschoorstra@outlook.com> * fix: advertise resolvable activation strategy type names When the registry has no preferred alias, fall back to the simple assembly-qualified name so Studio stores an identifier the resolver can load. FullName is not a registered alias. Co-authored-by: Sipke Schoorstra <sipkeschoorstra@outlook.com> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> |
||
|---|---|---|
| .. | ||
| IncidentStrategies | ||
| RuntimeAdmin | ||
| WorkflowActivationStrategies | ||