1.4.1

In this update, we've tackled an issue where responses lacking a body but with a specified return type would lead to the client returning the default value for that type, which could cause unexpected behavior. To enhance clarity and predictability in error handling, we have revised the implementation to throw an HttpContentException under these circumstances. This modification ensures developers are promptly informed about missing response bodies, thereby avoiding the unintentional use of default values.

We appreciate your ongoing support and engagement.