Skip to content
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.

Better error reporting #42

Closed
cgatian opened this issue Sep 28, 2017 · 3 comments
Closed

Better error reporting #42

cgatian opened this issue Sep 28, 2017 · 3 comments

Comments

@cgatian
Copy link

cgatian commented Sep 28, 2017

If husky is added into the pipeline to lint on precommit, you may encounter linting errors. Current the only way to see them is if you hover over the error message. Is there a better way in VS code to display these messages to the developer?

image

@cgatian
Copy link
Author

cgatian commented Sep 28, 2017

@KnisterPeter If you have any ideas in mind, I can take a look into it. Perhaps saying, "Commit failed" and append the error message?

@KnisterPeter
Copy link
Owner

I'll think about it. Thanks for reporting.

@KnisterPeter
Copy link
Owner

Currently I use execa to run git in a forked process. This returns the stdout of the process.

It maybe be possible to output the stdout result in a vscode.OutputPanel and open it.
This should be configurable like the task output.

KnisterPeter added a commit that referenced this issue Oct 5, 2017
Add option to open output panel after commit. Could be either never, always or onError.

Closes #42
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants