Restore Literal handling in ActivityExecutionContext.TryGet #7075
+116
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 3.5.2 removed code that handled
Literalobjects inActivityExecutionContext.TryGet(), breaking the common pattern of programmatically creating activities with literal inputs. This throwsInvalidOperationException: The memory block 'Elsa.Expressions.Models.Literal1[T]' does not exist.`Root Cause
When
Input<T>is constructed with aLiteral, the literal becomes theMemoryBlockReference. Unlike variables, literals hold values directly rather than storing them in the memory register. Without special handling,TryGetattempts to look up the literal in the register and fails.Changes
ActivityExecutionContext.TryGet(): Added early return whenblockReference is Literalto retrieve the value directlyUse Case
Activities that dynamically instantiate and configure other activities with literal values:
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
This change is