Skip to content

.NET: [Bug]: YAML validation is weak in some cases. Declarative.dll errors misleading or not self explainable #8015

Description

@dsslight

Description

For the Declarative workflow documentation
YAML validation is weak in some cases. For example, I can set an invalid value on SendActivity instead of text (like prompt.test, not prompt.text) and only get runtime errors about missing variables instead of YAML validation errors.
If I set a variable such as Topic.ToolResponse in YAML, even when the namespace is wrong, validation does not complain. Fixing this problem need to be done carefully, cos we have undocumented behavior about namespaces Topic vs Local here

In general I can only infer what went wrong from limited runtime errors produced by the declarative.DLL that executes the YAML instructions.
Dll errors quite limited and do not provide useful info, so I need to guess what's going on.
If declarative.dll code debuggable, would be great to have instruction on how to do it/turn it on.

Code Sample

Error Messages / Stack Traces

Package Versions

Microsoft.Agents.AI.Workflows.Declarative

.NET Version

.NET 10.0.300

Additional Context

documentation related issue

Activity

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

Metadata

Metadata

Labels

.NETUsage: [Issues, PRs], Target: .NetdeclarativeUsage: [Issues, PRs], Target: declarative agents and workflowsreproducedUsage: [Issues], Target: all issues that can be reproduced by the triage workflowworkflowsUsage: [Issues, PRs], Target: Workflows

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions