fix(fetch): Improved error handling when body does not exist in fetch client

[soartec-lab]

Status

READY

Description

fix #1854
The automatically generated source code has been changed as follows.

When includeHttpResponseReturnType is true (default):

+ const body = [204, 205, 304].includes(res.status) ? null : await res.text();
- const data: Pet = [204, 205, 304].includes(res.status) || !res.body ? {} : await res.json();
+ const data: showPetByIdResponse['data'] = body ? JSON.parse(body) : {};

-  return { status: res.status, data, headers: res.headers };
+  return { data, status: res.status, headers: res.headers } as showPetByIdResponse;

When includeHttpResponseReturnType is false:

+ const body = [204, 205, 304].includes(res.status) ? null : await res.text();
- const data: Pet = [204, 205, 304].includes(res.status) || !res.body ? {} : await res.json();
+ const data: Pets = body ? JSON.parse(body) : {};

-  return data as Pets
+  return data;

Related PRs

• feat(fetch): add type to response data in fetch client #1773
• feat(fetch): include error types in data type of fetch response #1776

Todos

• Tests
• Documentation
• Changelog Entry (unreleased)

Steps to Test or Reproduce

Both patterns of options you can see in the sample app.