Closed cesarsalgado closed 6 years ago
Thanks for the change @cesarsalgado, it looks like a good addition. Any chance of a test for it?
Hi @dareid , I added two tests to packet_test.go. Let me know if they are enough. Thanks
Perfect, thanks for the PR @cesarsalgado
Before the only way for the user to get the error was to call GetResultObject. However, the parse would also be called in this case and then the user wouldn't know (programatically) where the error came from. Off course, the librarie's user could make some string matching to try to deduce, but this is error prone and non scalable.