3 ms·
My condolences. Any open standard runs the risk of this happening. It's not a problem I think we'll ever solve.
by 999900000999 2y ago
My condolences. Any open standard runs the risk of this happening. It's not a problem I think we'll ever solve.
- marcosdumay 2y agoIn principle, if you make your standard extensible enough, people should stop sneaking data into comments or strings. ... What makes the GP's problem so much more amusing. XML was the last place I'd expect to see it.
- 999900000999 2y agoThat's assuming they know how to use it properly. Rest has this same issue. I've seen this when trying to integrate with 3rd party apis. Status Code 200 Body: Sorry bro, no data. Even then, this is subject to debate. Should a 404 only be used when the endpoint doesn't exist ? When we have no data to return, etc.
- Xelbair 2y agoi think that default REST is a bit problematic as it conflates transport protocol level errors with application logic ones. At least unless you use application/problem+json or application/problem+xml MIME types but those are still just in draft stage https://datatracker.ietf.org/doc/html/rfc9457#name-the-problem-details-json-ob https://datatracker.ietf.org/doc/html/rfc9457#name-the-probl...