Closed fbertone closed 1 year ago
This simply fixes #88 by emiting the same XML it receives from the device (after validation)
Well this actually fixes my issue, it doesn't change the fact that parseSOAPString outputs invalid XML
Coverage remained the same at 87.899% when pulling d4ac8c9c9e5a3e866f84834f57c5690d7639db57 on fbertone:patch-1 into a21199c93b0f9d52387e0f368d3425ac6cb6dff6 on agsh:master.
This simply fixes #88 by emiting the same XML it receives from the device (after validation)