-
Notifications
You must be signed in to change notification settings - Fork 210
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.
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
Stream response for HEAD endpoint #4245
Comments
Thanks for raising this @bkoelman Stream is used as a default if the response code is not in kiota/src/Kiota.Builder/KiotaBuilder.cs Line 1314 in 437045d
|
I've just updated to v1.14, which changes the return type to |
Thanks for confirming. We'll close this one for now. I believe this was resolved via #4367 |
I was wrong about this, the bug is still there. But the situation got worse than before. My OAS looks like this for the HEAD request: "responses": {
"200": {
"description": "The operation completed successfully.",
},
"304": {
"description": "The fingerprint of the HTTP response matches one of the ETags from the incoming If-None-Match header.",
},
"400": {
"description": "The query string is invalid."
} Today kiota makes the return type "responses": {
"200": {
"description": "The operation completed successfully."
}
} it generates |
Re-opening. The fix here would involve checking the request method( |
When a HEAD endpoint contains only responses without a body (which should always be the case), Kiota generates
Task<Stream?>
as the response type. Is that intentional? I would have expected the return type to beTask
.Repro steps:
Used command line:
Generated client usage:
The text was updated successfully, but these errors were encountered: