Feature request: include wire with FormError
11 views
Skip to first unread message
Casey Deccio
Apr 29, 2013, 5:31:20 PM4/29/13
to dnspyth...@googlegroups.com
Hi Bob,
It would really be useful to have the raw wire that caused a FormError to be raised (e.g., as an instance variable in the Exception), to help troubleshoot why it was raised, etc. This is mostly for messages received from the network, as there is no way (that I can see) to preserve that value otherwise. I could try to modify the code for a potential proof-of-concept, but I'd thought I would check with you first, as you would probably have more insight as to how do this properly with the current framework. What do you think?
Casey
It would really be useful to have the raw wire that caused a FormError to be raised (e.g., as an instance variable in the Exception), to help troubleshoot why it was raised, etc. This is mostly for messages received from the network, as there is no way (that I can see) to preserve that value otherwise. I could try to modify the code for a potential proof-of-concept, but I'd thought I would check with you first, as you would probably have more insight as to how do this properly with the current framework. What do you think?
Casey
Reply all
Reply to author
Forward
0 new messages