From 3423c79e49d1cbc68a6a1d066b6eac92fd30cc3e Mon Sep 17 00:00:00 2001 From: Brian O'Kelley Date: Mon, 5 Jan 2026 08:11:57 -0500 Subject: [PATCH] Add explicit type to error.json details property MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The `details` property now specifies `"type": "object"` with `"additionalProperties": true`, making the schema explicit about what types are accepted. Fixes #343 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 --- .changeset/error-details-type.md | 7 +++++++ static/schemas/source/core/error.json | 4 +++- 2 files changed, 10 insertions(+), 1 deletion(-) create mode 100644 .changeset/error-details-type.md diff --git a/.changeset/error-details-type.md b/.changeset/error-details-type.md new file mode 100644 index 0000000000..c9ee80212e --- /dev/null +++ b/.changeset/error-details-type.md @@ -0,0 +1,7 @@ +--- +"adcontextprotocol": patch +--- + +Add explicit type definition to error.json details property + +The `details` property in core/error.json now explicitly declares `"type": "object"` and `"additionalProperties": true`, consistent with other error details definitions in the codebase. This addresses issue #343 where the data type was unspecified. diff --git a/static/schemas/source/core/error.json b/static/schemas/source/core/error.json index c12cfd1675..efbe3abf0c 100644 --- a/static/schemas/source/core/error.json +++ b/static/schemas/source/core/error.json @@ -27,7 +27,9 @@ "minimum": 0 }, "details": { - "description": "Additional task-specific error details" + "type": "object", + "description": "Additional task-specific error details", + "additionalProperties": true } }, "required": ["code", "message"],