Adapter mixin causes error when API returns empty object & 204 about ember-fetch HOT 5 CLOSED

I just want to mention that we are moving fetch support to Ember Data itself : emberjs/data#5386

from ember-fetch.

hey @simonihmig!

Seems like something that should be changed in Mirage. According to httpstatus, A 204 response is terminated by the first empty line after the header fields because it cannot contain a message body.

The logic in ember-fetch assumes that a 204 is being implemented this way

from ember-fetch.

@nlfurniss hey, yes, I should probably create an issue for mirage as well. But I nevertheless think this could maybe be handled a bit better here as well, i.e. ignore any payload in the adapter mixin for a 204 response. Don't you think?

from ember-fetch.

Hi @simonihmig

To be a drop-in replacement, I think this should behave the same way as before, i.e. return undefined (or maybe { data: null } as it was before)!?

But the PR (it's same as now) you linked, the handling is to return { data: null }

if (response.ok && (status === 204 || status === 205 || requestData.method === 'HEAD')) {
    payload = { data: null };
}

Is it the expected output? Or the payload should be an empty string in 204 case?

from ember-fetch.

Closing this, as this has been fixed in Mirage, and the fetch adapter mixin is deprecated anyway.

from ember-fetch.