microsoft / microsoft/agent-framework-durable-extension
.NET sample: Reject JSON null external history documents
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 10
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 9
Description
Follow-up to #99.
The custom JSON-file history sample currently treats a complete JSON null document as an empty transcript. Change restored-session reads to throw JsonException instead, while retaining the explicitly allowed missing-file path for new history, and add a regression test.
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 by locating the custom JSON-file history sample and its restored-session read path. Add a regression test covering a complete JSON null document while preserving the missing-file behavior for new history. Done means restored reads throw JsonException and missing files remain allowed for new history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, json
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100