Skip to content

0.134.0: ApiError.fields_refusal reads everything a read's fields list got wrong - #14

Merged
tmoosting merged 1 commit into
mainfrom
fields-refusal
Nov 17, 2026
Merged

tmoosting merged 1 commit into
mainfrom
fields-refusal

Conversation

@tmoosting

Copy link
Copy Markdown
Member

A read whose fields names fields the type does not have is one 422 with param fields. onlyworlds.com now names every unknown name in it, and the error carries unknown_fields, types_with_field and allowed_fields. ApiError.fields_refusal returns the three as served.

🤖 Generated with Claude Code

…t got wrong

A read whose fields names fields the type does not have is one 422 with
param fields. onlyworlds.com now names every unknown name in it, and the
error carries unknown_fields, types_with_field and allowed_fields.
fields_refusal returns the three as served, None for any other error; the
wire test allows the three keys only when the document declares them, and
then holds the property to each.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@tmoosting
tmoosting merged commit 6a30685 into main Nov 17, 2026
10 checks passed
@tmoosting
tmoosting deleted the fields-refusal branch November 17, 2026 08:26

This branch was previously deployed

1 inactive deployment
pypi — 6a30685b Deployed Nov 17, 2026 by tmoosting via publish #214
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.

1 participant