cm0002@lemmy.world to Programmer Humor@programming.dev · 4 days agoYes, But...lemmy.mlimagemessage-square84fedilinkarrow-up1756arrow-down19cross-posted to: programmerhumor@lemmy.ml
arrow-up1747arrow-down1imageYes, But...lemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 4 days agomessage-square84fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squaremmddmm@lemm.eelinkfedilinkarrow-up85·4 days agoAnd no error message… I guess that’s how it’s done. Yeah.
minus-squareThorry84@feddit.nllinkfedilinkarrow-up20·4 days agoDoesn’t matter, the client ignores the error anyways.
minus-squarenogooduser@lemmy.worldlinkfedilinkEnglisharrow-up1·3 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-squarenaught@sh.itjust.workslinkfedilinkarrow-up5·3 days agoThis is always how graphql works :)
minus-squarePlutoVolcano@lemm.eelinkfedilinkEnglisharrow-up7·edit-24 days agoGetting only a message with no error indicator isn’t much better either
minus-squaremarlowe221@lemmy.worldlinkfedilinkEnglisharrow-up5·4 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.
This is always how graphql works :)
Getting only a message with no error indicator isn’t much better either
Ah, I see you too have run code in Azure Functions…