Skip to content

Keep raw response when pending result decoding fails - #292

Open
EhsanAzish80 wants to merge 1 commit into
modelcontextprotocol:mainfrom
EhsanAzish80:fix/pending-response-diagnostics
Open

EhsanAzish80 wants to merge 1 commit into
modelcontextprotocol:mainfrom
EhsanAzish80:fix/pending-response-diagnostics

Conversation

@EhsanAzish80

@EhsanAzish80 EhsanAzish80 commented Sep 24, 2026 •

Copy link
Copy Markdown

When a response cannot decode as the expected result type, TypeMismatchError now includes the expected type, raw value and underlying decoding error. This gives clients enough information to diagnose issue #220 without changing how valid responses decode.

Tests: 554 Swift tests passed locally, including malformed, valid and non-JSON response cases.

AI assistance was used to write the code and tests.The diff was checked and the tests were run locally.

@varun06

varun06 commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Hi @EhsanAzish80, thanks for this PR! I've reviewed it and it looks good to merge.

Could you please rebase it onto the latest main? CI was broken on macOS runners for every PR (a toolchain/SDK mismatch, fixed in #306), so rebasing will pick up the fix and give us a green run. I'll review and merge once it's updated.

If you're no longer able to work on this, no problem: just let us know. If we don't hear back in about two weeks, we may carry the change forward in a new PR, with credit to you.

@EhsanAzish80
EhsanAzish80 force-pushed the fix/pending-response-diagnostics branch from 32433ad to 4fd3fe1 Compare October 22, 2026 15:27
@EhsanAzish80
EhsanAzish80 force-pushed the fix/pending-response-diagnostics branch from 4fd3fe1 to 277f5b7 Compare October 22, 2026 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants