Address wrapping of errors into client errors

[abbiemery]

I'm not sure if having a custom client result and wrapping the errors with the enum is the way forward. It might be worth discussing and weighing put the pros and cons.

[abbiemery]

Could use something like this instead? Result<T, Box<dyn Error>>

[tpoliaw]

Box<dyn Error> is the equivalent of raising Exception for everything in Python.

It depends if anyone is ever going to want to handle the error in any way other than crashing. I think it would be good to differentiate between errors in glazed which should be logged and handled, and the errors forwarded to graphql clients using the service, eg, Tiled server error: error sending request for url (http://localhost:8000/api/v1/search/bac3d072-13d1-4fa3-91ea-8c4af526fbda) is useful for glazed internally but clients might only be interested that the tiled server is not available.

What is the problem with using the ClientError enum?