EG: Not well-formed XML starting with "<!" at position 0 at JI.fatalError (/Users/<USER>/.vscode/extensions/anweber.vscode-httpyac-6.16.3/dist/extension.js:157:3567) at LPe (/Users/<USER>/.vscode/extensions/anweber.vscode-httpyac-6.16.3/dist/extension.js:155:3388) at nHt (/Users/<USER>/.vscode/extensions/anweber.vscode-httpyac-6.16.3/dist/extension.js:154:20087) at MPe.parse (/Users/<USER>/.vscode/extensions/anweber.vscode-httpyac-6.16.3/dist/extension.js:154:17785) at KPe.parseFromString (/Users/<USER>/.vscode/extensions/anweber.vscode-httpyac-6.16.3/dist/extension.js:157:1165) at rJ (/Users/<USER>/.vscode/extensions/anweber.vscode-httpyac-6.16.3/dist/extension.js:280:28801) at Object.beforeLoop (/Users/<USER>/.vscode/extensions/anweber.vscode-httpyac-6.16.3/dist/extension.js:280:29556) at Wte.intercept (/Users/<USER>/.vscode/extensions/anweber.vscode-httpyac-6.16.3/dist/extension.js:27:3784) at processTicksAndRejecti...
That's right. It's bad when you can only nod when someone explains a bug. I will fix it. It came in due to the changed behavior of xmldom. I noticed it, but didn't think about it any further
I was running HttpYak agains a basic local server that was outputting sample HTML/JSON data and noticed that
text/html
for JSON would cause the extension to raise exception<!doctype html />
also cause exceptions as pretty printer does not like itI think both issues are due to the XML parser trowing exceptions:
https://github.com/AnWeber/httpyac/compare/6.16.0...6.16.1#diff-7f25891c1de6aa3847cf8cb9c1bbf5b6f7e512662b18a71d5a236061a9ed140dR23-R26
Sample Stack Trace:
Platform: MacOS Version: 6.16.3