Skip to content

Read writeOnly so required write-only fields don't break response schemas #63

Open

Description

@mattzcarey

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.

Found by the response checks in cloudflare/mcp#301.

Activity

  1. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions