That makes sense. I didn't know about the other error information that seraph adds. The reason I added this though is that I wanted validation errors to deliver true errors and not just a text string. Is there any way to make the error handling part of seraph generic so that we can re-use for the validations? We wouldn't need to expose these errors to end users - just ensure that every error returned by Seraph follows the same structure. By abstracting as well we can add information to the errors, if relevant, in a single location.