Closed TheJakeSchmidt closed 8 years ago
@TheJakeSchmidt mind adding a description to your PR? A quick summary about the motivation and solution should work.
+1 to Grayson's comment. Please explain the change and link to the relevant GH issue (#131) in the commit message.
Minor comments besides that but the approach looks good.
Thanks for the reviews! I added a description to the PR and the initial commit, and responded to both comments.
LGTM.
Please add an entry to the changelog and I'll merge this.
This partially fixes GitHub issue #131.
This is not a complete solution, as the error message is still opaque, but it's an improvement. Throwing the error at struct creation time instead of at serialization time makes it clearer which struct has a bad field, and makes it easier for TChannel clients to handle, since TChannel doesn't seem to provide a way to catch response serialization exceptions.