Better output formatting and error handling #71
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What code changed, and why?
Previously when running previews, the output was a dump of JSON. This is not always very friendly. This adapts functions from DAS UI to format returns. In addition, extra data such as printed lines and instrumentation metrics are formatted much more clearly. The response is always at the (scrolled to) bottom so it is immediately visible.
In addition, non-200 API responses are handled and surfaced as an error pop-up instead of printing JSON to the results output window. This make is far easier to tell that something has gone wrong, and the EOPA generated message is presented to the user along with the API response code.
Definition of done
The user has nicely formatted output when running EOPA previews through VS Code.
How to test
You can install either from source code or from GitHub.
Install from source
npm install
.Install from GitHub
vscode-styra-2.0.0-next.1.vsix
.code --install-extension vscode-styra-2.0.0-next.1.vsix
Exercise the Code