Skip to content

fix(composer): expand template expressions in elicitation messages#4313

Open
saschabuehrle wants to merge 1 commit intostacklok:mainfrom
saschabuehrle:fix/issue-4312
Open

fix(composer): expand template expressions in elicitation messages#4313
saschabuehrle wants to merge 1 commit intostacklok:mainfrom
saschabuehrle:fix/issue-4312

Conversation

@saschabuehrle
Copy link

Bug

#4312 — Template expressions like {{.params.owner}} in elicitation step message fields are passed through as raw placeholders instead of being expanded.

Fix

Adds template expansion for step.Elicitation.Message in executeElicitationStep() before passing it to RequestElicitation(). This mirrors how executeToolStep() already expands step.Arguments through the template expander (line ~404).

The expansion wraps the message string in a temporary map to reuse the existing public TemplateExpander.Expand() interface, keeping the change minimal and consistent with the established expansion pattern.

Testing

  • Added TestWorkflowEngine_ElicitationMessageTemplateExpansion integration test that verifies {{.params.repo}} and {{.params.env}} placeholders in an elicitation message are expanded to their resolved values before reaching the SDK elicitation requester.

Happy to address any feedback.

Greetings, saschabuehrle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant