cm0002@lemmy.world to Programmer Humor@programming.dev · 12 days agoYes, But...lemmy.mlexternal-linkmessage-square66fedilinkarrow-up1682arrow-down19cross-posted to: programmerhumor@lemmy.ml
arrow-up1673arrow-down1external-linkYes, But...lemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 12 days agomessage-square66fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squaremmddmm@lemm.eelinkfedilinkarrow-up73·12 days agoAnd no error message… I guess that’s how it’s done. Yeah.
minus-squareThorry84@feddit.nllinkfedilinkarrow-up17·12 days agoDoesn’t matter, the client ignores the error anyways.
minus-squarenogooduser@lemmy.worldlinkfedilinkEnglisharrow-up1·11 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-squarePlutoVolcano@lemm.eelinkfedilinkEnglisharrow-up6·edit-212 days agoGetting only a message with no error indicator isn’t much better either
minus-squaremarlowe221@lemmy.worldlinkfedilinkEnglisharrow-up5·12 days agoAh, I see you too have run code in Azure Functions…
minus-squarenaught@sh.itjust.workslinkfedilinkarrow-up4·12 days agoThis is always how graphql works :)
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
Ah, I see you too have run code in Azure Functions…
This is always how graphql works :)