.NET: Strictly reject ambiguous child workflow result controls

Open
#107 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 10 days

@LE0-Lin is already working on this.

Since Oct 4, 2026.

  • #133 by @LE0-Lin — open

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp

Research direction

Start at the child workflow result deserialization entry point and review the targeted System.Text.Json options, especially AllowDuplicateProperties. Add focused camelCase/PascalCase and duplicate-control tests, while preserving result-only fallback behavior when JsonException is raised.

Written by the indexing model from the issue text.

Description

Follow-up to #94.

Child workflow results are deserialized case-insensitively. Conflicting known properties such as events/EVENTS, haltRequested, result, or sentMessages should be rejected before trusted controls are applied.

Use targeted System.Text.Json options with AllowDuplicateProperties = false, preserve result-only fallback behavior on JsonException, and add focused camelCase/PascalCase and duplicate-control tests.

This is intentionally deferred to avoid rewriting the existing stacked PRs again.

Dominant language
Python
Stars
24
Forks
12
Avg merge
5d 13h
Merged PRs (30d)
16

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/agent-framework-durable-extension

All issues in microsoft/agent-framework-durable-extension

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.