Add support for content item-backed workflow definitions

Introduced a `ContentItemWorkflowDefinitionStore` and related mappers, extensions, and index updates to manage workflow definitions as content items. Refactored the system to replace existing handlers with a store-based approach and optimized querying and mapping workflows.
This commit is contained in:
Sipke Schoorstra 2025-02-13 23:39:56 +01:00
parent 0c53c7095c
commit 7b5aa6073d
2 changed files with 4 additions and 4 deletions

View file

@ -31,5 +31,5 @@ public class OrderDefinition<T, TProp>
/// <summary>
/// The key selector to use to order the results.
/// </summary>
public Expression<Func<T, TProp>> KeySelector { get; set; } = default!;
public Expression<Func<T, TProp>> KeySelector { get; set; } = null!;
}

View file

@ -51,12 +51,12 @@ public class WorkflowDefinitionSummary
/// <summary>
/// The version ID of the workflow definition.
/// </summary>
public string Id { get; set; } = default!;
public string Id { get; set; } = null!;
/// <summary>
/// The ID of the workflow definition.
/// </summary>
public string DefinitionId { get; set; } = default!;
public string DefinitionId { get; set; } = null!;
/// <summary>
/// The name of the workflow definition.
@ -96,7 +96,7 @@ public class WorkflowDefinitionSummary
/// <summary>
/// The materializer name of the workflow definition.
/// </summary>
public string MaterializerName { get; set; } = default!;
public string MaterializerName { get; set; } = null!;
/// <summary>
/// The timestamp when the workflow definition was created.