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

@azure-tools/typespec-azure-resource-manager/arm-post-operation-response-codes rule should it allow 204 isntead of 200 if there is no body #857

Closed
timotheeguerin opened this issue May 17, 2024 · 1 comment
Closed

@azure-tools/typespec-azure-resource-manager/arm-post-operation-response-codes rule should it allow 204 isntead of 200 if there is no body #857

timotheeguerin opened this issue May 17, 2024 · 1 comment
Labels
needs-area

Comments

@timotheeguerin
Copy link
Member

Playground

This is our nobody-action sample that emit a warning, is the rule incorrect or the response should change to OkResponse from void
@timotheeguerin timotheeguerin transferred this issue from Azure/azure-rest-api-specs May 17, 2024
@markcowl
Copy link
Member

markcowl commented May 29, 2024 •
edited

No, the rule is correct, the actual lintdiff rule requires a 202 and no other response for async POST with no response body. You do this by using 'never' with the response.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs-area
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@timotheeguerin @markcowl