NOTE: Following upstream changes, Orchestra no longer includes the explain string in the thrown exception. In your applications, catch exceptions and output your own explain strings using the explain data in the exception. I recommend Expound, since it works well and is explicitly tested to do so with Orchestra.
This seems like a very sensible change. It would be incredibily useful if a plug-and-play example was provided in the README as to how to catch an orchestra exception and get the old behaviour using that exception as this seems to be a very common case.
This seems like a very sensible change. It would be incredibily useful if a plug-and-play example was provided in the README as to how to catch an orchestra exception and get the old behaviour using that exception as this seems to be a very common case.