[Feat] Error message from exceptions about lighthouse HOT 6 CLOSED

@olivernybroe can this be closed as of #235 ?

from lighthouse.

Hi @olivernybroe,
Im not aware of what you mean, i know you can overwrite the error function, just been added to the repo on latest commits.
I personally, working with react, im able to process exceptions errors, 500, all, as it comes with no additional setup.

Could you provide more info?

from lighthouse.

@kikoseijo Oh If I can overwrite the error function then I can prob. just implement it myself.

But what I mean is in Laravel when I implement the Responsable interface, Laravel will render my exception accordingly to the toResponse($request) method.
I for example like throwing exceptions when something is wrong and then handling them in the exceptionshandler and render them to the front end with the toResponse($request) method.

So my proposal is to have an interface like this, but just for rendering the exception for the errors array in graphql.

from lighthouse.

I wonder if this is posible,
but i guess the Graphql has a try-catch and does its own thing.

Maybe this helps you:

https://github.com/nuwave/lighthouse/blob/882a1b21508f60fcadb21ec7b8bdc320a270a649/src/Support/Traits/CanFormatError.php

from lighthouse.

Hey @olivernybroe

Would this help with error messages such as this? It would be nice to have errors as JSON to directly view them in one of the GraphQL tools. Often, i end up copy-pasting the query out of there and calling it directly in the browser to see the error output.

from lighthouse.

@spawnia that is another problem, but not the one I am trying to solve here. I merely won't to implement a interface on my exception class, and if this interface exists, then a specific method on the exception tells how to render the exception in the errors array on the output.

from lighthouse.