Skip to content

fix: expose write-only field metadata - #80

Closed
sansynx wants to merge 1 commit into
cloudflare:mainfrom
sansynx:fix/write-only-field-metadata
Closed

sansynx wants to merge 1 commit into
cloudflare:mainfrom
sansynx:fix/write-only-field-metadata

Conversation

@sansynx

@sansynx sansynx commented Nov 1, 2026

Copy link
Copy Markdown

Read writeOnly from property schemas and reference chains, and expose it as Field::is_write_only() and Field.writeOnly in plugins. Required properties stay in shared models so generators can omit them from responses without dropping request fields.

The plugin interface moves to forge:plugin@0.4.0; existing plugins need rebuilding.

Fixes #63.

@sansynx sansynx closed this Nov 1, 2026
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.

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

1 participant