Hey all sorry for another newbie question. I've just been reading about errrors and how you are supposed to use resolve-as. http://lacinia.readthedocs.io/en/latest/resolve/resolve-as.html To me it sounds like you would wrap your resolver function with a try catch, then in the catch call

(resolve-as resolved-value {:message "something when wrong"})

am i along the right track?

Yes, that's that's pretty much exactly how it goes. Earlier versions of Lacinia would catch exceptions inside field resolver functions for you, but that turned out to be unnecessary overhead most of the time, and got in the way of actually debugging real problems. Please feel free to suggest improvements to the documentation, if this was not clear.

:thumbsup:

thanks a bunch

Yeah i'm just using it in my new project

I'll see if i can do a write up afterwards or something