microsoft / microsoft/agent-framework-durable-extension
.NET: Strictly reject ambiguous child workflow result controls
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 10
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 9
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- csharp
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100