Avoid printing invalid pointer when api returns 404

[amw]

Fixes the pointer for 404 results.

Checklist

• PR only contains one change (considered splitting up PR)
• unit-test added
• documentation updated
• CHANGELOG.md updated (only for user relevant changes)
• author name in AUTHORS

[codecov]

Codecov Report

Merging #599 into master will decrease coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #599      +/-   ##
==========================================
- Coverage   96.11%   95.98%   -0.14%     
==========================================
  Files          56       56              
  Lines        2859     2866       +7     
==========================================
+ Hits         2748     2751       +3     
- Misses        111      115       +4

Impacted Files	Coverage Δ
example/tests/test_model_viewsets.py	100% <100%> (ø)	⬆️
example/tests/integration/test_polymorphism.py	96.74% <0%> (-3.26%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b1acaf1...dbe02e4. Read the comment docs.

[sliverc]

Thanks for your contribution and well spotted, the pointer is invalid indeed.

The specification doesn't specifically clarify what to do in case of a 404 error. In this discussion though they suggest not to add a pointer in case of 404. Sounds kind of logical to me as there is not data actually returned so they can't be a pointer.

Could you adjust your PR so it doesn't add a pointer in case of 404?

[amw]

I've removed the source entirely for 404 errors.

[sliverc]

Thanks.