Skip to content

Consider implementing RequestContent<T> when deriving Model #1860

@heaths

Description

@heaths

For top-level request models that are for required parameters - and maybe we need an attribute to identify these - we should consider implementing RequestContent<T>. Or maybe we just need a separate derive macro (or attribute macro) for this. It's very boiler plate.

See Azure/typespec-rust#124 (comment) for context

Metadata

Metadata

Assignees

No one assigned

    Labels

    Azure.CoreThe azure_core crateClientThis issue points to a problem in the data-plane of the library.blocking-releaseBlocks release

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions