cm0002@lemmy.world to Programmer Humor@programming.dev · 1 month agoYes, But...lemmy.mlexternal-linkmessage-square77fedilinkarrow-up1726arrow-down19
arrow-up1717arrow-down1external-linkYes, But...lemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 1 month agomessage-square77fedilink
minus-squaremmddmm@lemm.eelinkfedilinkarrow-up79·1 month agoAnd no error message… I guess that’s how it’s done. Yeah.
minus-squareThorry84@feddit.nllinkfedilinkarrow-up20·1 month agoDoesn’t matter, the client ignores the error anyways.
minus-squarenogooduser@lemmy.worldlinkfedilinkEnglisharrow-up1·1 month 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-21 month agoGetting only a message with no error indicator isn’t much better either
minus-squaremarlowe221@lemmy.worldlinkfedilinkEnglisharrow-up5·1 month agoAh, I see you too have run code in Azure Functions…
minus-squarenaught@sh.itjust.workslinkfedilinkarrow-up5·1 month 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 :)