@cm0002@lemmy.world to Programmer Humor@programming.dev • 16 days agoYes, But...lemmy.mlimagemessage-square78fedilinkarrow-up1766arrow-down19cross-posted to: programmerhumor@lemmy.ml
arrow-up1757arrow-down1imageYes, But...lemmy.ml@cm0002@lemmy.world to Programmer Humor@programming.dev • 16 days agomessage-square78fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-square@mmddmm@lemm.eelinkfedilink85•16 days agoAnd no error message… I guess that’s how it’s done. Yeah.
minus-square@Thorry84@feddit.nllinkfedilink20•16 days agoDoesn’t matter, the client ignores the error anyways.
minus-square@nogooduser@lemmy.worldlinkfedilinkEnglish1•15 days 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@PlutoVolcano@lemm.eelinkfedilinkEnglish7•edit-216 days agoGetting only a message with no error indicator isn’t much better either
minus-square@marlowe221@lemmy.worldlinkfedilinkEnglish5•16 days agoAh, I see you too have run code in Azure Functions…
And no error message…
I guess that’s how it’s done. Yeah.
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.
Getting only a message with no error indicator isn’t much better either
This is always how graphql works :)
Ah, I see you too have run code in Azure Functions…