You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Forge doesn't read writeOnly, so a required write-only field stays required in response schemas. The API never returns these fields, so every real response fails.
Example: hyperdrive-database-full requires password, which is writeOnly ("The API never returns this write-only value"). Every Hyperdrive config response schema then requires origin.password.
12 schemas in the spec have a required writeOnly field.
Fix: add Field::is_write_only, like is_read_only, so generators can drop these fields from responses.
changed the title [-]writeOnly isn't read, so required write-only fields stay required in responses[/-][+]Read writeOnly so required write-only fields don't break response schemas[/+]on Oct 21, 2026
Activity
[-]writeOnly isn't read, so required write-only fields stay required in responses[/-][+]Read writeOnly so required write-only fields don't break response schemas[/+]