• 2
    I was waiting for this answer 😆
  • 3
    Fuckkkk Gql. Srsly.
    Returning 200 ok and wrapping the actual 50? error?

    Fuck it with a sideways cactus.
  • 5
    @magicMirror this has nothing to do with graphql. People do this shit with REST, too.
  • 0
    @Lensflare That reminds me:
    Fuckkkk idiot devs.
  • 0
    Oh I know the pain when people who barely can wrap their head around rest start pushing GraphQL for fucking everything. There will be special place in hell. My personal pain and suffering i deal every day some ingenious guy thought we should bring down db connections for accessing data, which itself is good idea, by implementing graphql proxying now instead on http1.x cause fuck reasoning.
  • 1
    @magicMirror We would return the proper error code, GraphQL is for the body and sits on the top of HTTP.

    Honestly, it's kinda neat, I almost never needed to cross data, ad-hoc request, and so on
Add Comment