Client throws NoSuchMethodError on unexpected primary data

[otopba]

Hi!
Method deleteResourceAt passes null decodePrimaryData to _call.
So if server will return something on DELETE request we will have exception inside Document.fromJson function

[f3ath]

The standard does not allow returning primary data on resource deletion except for the 202 Accepted response. Other than that, there may be 3 general cases:

• no content
• error response
• meta data

neither of which is expected to have primary data. So I'm not sure if I understand the issue here. Would you mind providing an example of server response?

[otopba]

@f3ath You are right about the standard. But maybe the library should handle this response correctly. Because now it throws NoSuchMethodError

Of course, this is the wrong server behavior. But it seems that the client should not break in this case

Example of the response:

{
   "data":{
      "id":"4f07091d-cbde-4475-8639-031fafa785ea",
      "type":"post"
   }
}

[f3ath]

Yep that's a perfectly valid point.

[f3ath]

A null check should be sufficient then. @otopba do you have an opinion on how this case should be handled?

[otopba]

@f3ath
I think that the library can ignore the body of the response in this case. Because this answer is not made by standard

[f3ath]

Fix released in v4.2.2. @otopba please confirm the issue is resolved.

[otopba]

@f3ath Thank you. Now it works great 🤗