All decoders follow rule: if a status is 404 it returns empty or null value

[vitalijr2]

Now some decoders follow this rule but other don't.

After 11.6 the flag decode404 doesn't work as it is described in the documentation. In new implementation a response body will be ignored, not decoded. I propose to replace decode404 with dismiss404 following the comment #1529 (comment)

Fixes #1595

[vitalijr2]

Should I update the changelog?
This change is important but the changelog hasn't updated since 10.9.

[velo]

Should I update the changelog? This change is important but the changelog hasn't updated since 10.9.

Since we started doing GitHub releases, we pretty much stop updating the changelog

May be needs a final entry saying so

[ugrepel]

Cool, thanks for fixing this. I've got a question however: is there any reason why the decoders distinguish between 204/404 decoding to (if defined) an empty version of the required type (e.g. an empty List), and, with other status codes, a null body, decoding to null?

[vitalijr2]

Good note.

I suppose that we should use emptyValueOf for any cases when a response body is null or cannot be decoded: 204, 205, 404 (optional) and just body is null with any other HTTP status code.

The code

if (response.body() == null) return null;

is too old, from first implementation, e. g. GsonDecoder.