ensure 304 response code does not throw
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start by reviewing the implementation and tests changed for empty 204 responses in microsoft/kiota issue 4190, then locate the corresponding response-handling path in kiota-python. Extend the existing behavior to cover HTTP 304 responses and add or update a test demonstrating that an empty 304 response does not throw.
Written by the indexing model from the issue text.
Description
when working on https://github.com/microsoft/kiota/issues/4190, we ensured 204 and other status codes with empty responses would not throw, we should do the same work for 304
- Dominant language
- Python
- Stars
- 31
- Forks
- 39
- Avg merge
- 11h 45m
- Merged PRs (30d)
- 42
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.
More from microsoft/kiota-python
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
microsoft/kiota-python#737 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/kiota-python#722 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 18/100
microsoft/kiota-python#533 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/kiota-python#501 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/kiota-python#490 · 1 comment ·
All issues in microsoft/kiota-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100