Shodai Suzuki

@nimo23 it's good. I'll close this issue and reopen it if you need it again.

@nimo23 I agree, I think it's good to support `not content`. However, there are many things to consider before and after `fetch', and we wanted to make the automatically generated...

OK, I'll think about this, so give me some time and this issue be reopened.

I have a couple ideas: ### 1. Check `res.body` In this case, you can simply remove the error since it doesn't depend on the status code. ```diff export const listPets...

Thank you for your reply. I agree with your opinion. I will wait for more options to gather.

Thank you for putting this together. I understand that you have merged both of my ideas. I completely agree with this, so I would like to implement this.

Perhaps this issue was fixed in #1958? so i'll close this.

Hi @thegenius, Thanks for making a good issue. We have tests in the `tests` directory. In this case, I think you can add a test by adding the `fomat: int64`...

Thank you for nice enhance ! I don't want to include the `hooks` concerns in the `fetch` package alone, so give me some time to think about how to get...

I've thought about this, and I'd like to have no `query` concerns in the `fetch` package. But that would require me to do more refactoring, so I'll make another one...