Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider implementing RequestContent<T> when deriving Model #1860

Open
heaths opened this issue Oct 21, 2024 · 0 comments
Open

Consider implementing RequestContent<T> when deriving Model #1860

heaths opened this issue Oct 21, 2024 · 0 comments
Labels
Azure.Core The azure_core crate Client This issue points to a problem in the data-plane of the library. design-discussion An area of design currently under discussion and open to team and community feedback.

Comments

@heaths
Copy link
Member

heaths commented Oct 21, 2024

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 https://github.com/Azure/typespec-rust/pull/124#discussion_r1807053182 for context
@heaths heaths added Client This issue points to a problem in the data-plane of the library. design-discussion An area of design currently under discussion and open to team and community feedback. Azure.Core The azure_core crate labels Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Azure.Core The azure_core crate Client This issue points to a problem in the data-plane of the library. design-discussion An area of design currently under discussion and open to team and community feedback.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@heaths