microsoft / microsoft/kiota-ruby
StandardError raised if no response content type found for deserialization
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5
- Forks
- 8
- Avg merge
- 11h 9m
- Merged PRs (30d)
- 24
Description
Some requests for example https://graph.microsoft.com/v1.0/identityProtection/riskyUsers/confirmCompromised may return a status 204 reason No Content and an empty response body.
@status=204 @reason_phrase="No Content" @response_body=""
This should not be treated as a fatal error and the send_async(request_info, factory, errors_mapping) method should just return an empty body
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the send_async(request_info, factory, errors_mapping) method and trace how a 204 response with an empty body reaches deserialization. Use the provided No Content example to verify that the request no longer raises StandardError and instead returns an empty body.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100