.NET sample: Reject JSON null external history documents

Open
#105 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.

  • #132 by @LE0-Lin — open

Assessment

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

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.

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.

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.