Skip to content

Rust Guidelines: RequestContent parameters should not be required to be named content #9921

Description

@azure-sdk-automation

Bad code snippet:

pub async fn restore_secret(&self, parameters: RequestContent<RestoreSecretParameters>, options: Option<SecretClientRestoreSecretOptions>) -> Result<Response<Secret>> {}

What it should do:
The APIView guidelines are outdated here. RequestContent<T> parameters should not be enforced to use the name content going forward, so parameters should be accepted as valid.

Good code snippet:

pub async fn restore_secret(&self, parameters: RequestContent<RestoreSecretParameters>, options: Option<SecretClientRestoreSecretOptions>) -> Result<Response<Secret>> {}

Metadata

Metadata

Assignees

No one assigned

    Labels

    customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-triageWorkflow: This is a new issue that needs to be triaged to the appropriate team.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions