@[email protected] to Programmer [email protected] • 3 months agoYes, But...lemmy.mlimagemessage-square78fedilinkarrow-up1762cross-posted to: [email protected]
arrow-up1762imageYes, But...lemmy.ml@[email protected] to Programmer [email protected] • 3 months agomessage-square78fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilink84•3 months agoAnd no error message… I guess that’s how it’s done. Yeah.
minus-square@[email protected]linkfedilinkEnglish7•edit-23 months agoGetting only a message with no error indicator isn’t much better either
minus-square@[email protected]linkfedilink20•3 months agoDoesn’t matter, the client ignores the error anyways.
minus-square@[email protected]linkfedilinkEnglish1•3 months agoThis is very frustrating! I get so many requests from customers asking why we returned response code 400 when we gave a description of the problem in the response body.
minus-square@[email protected]linkfedilinkEnglish5•3 months agoAh, I see you too have run code in Azure Functions…
And no error message…
I guess that’s how it’s done. Yeah.
Getting only a message with no error indicator isn’t much better either
Doesn’t matter, the client ignores the error anyways.
This is very frustrating! I get so many requests from customers asking why we returned response code 400 when we gave a description of the problem in the response body.
Ah, I see you too have run code in Azure Functions…
This is always how graphql works :)