"Resolver specified in schema not provided" could be clearer about lacinia

[hlship]

I'll think about it; I obviously use Pretty (https://github.com/AvisoNovate/pretty) so I'm used to seeing the exception info map along with the message, so I prefer for the message to not be redundant.

[vemv]

What was the issue's resolution?

It's not that redundant to show a diagnostic in the message. Under my reloaded workflow this is all I see initially after a failed (reset):

Execution error (ExceptionInfo) at com.walmartlabs.lacinia.util/attach-callbacks$fn (util.clj:45).
Resolver specified in schema not provided.

I can type (.printStackTrace *e), sure, but that's more steps to type/remember. Also for many cases I don't particularly need the whole stacktrace, simply a diagnostic would give me all I need and save the scanning through noise.