Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Better error logging #34

Open
chriskuech opened this issue Sep 15, 2019 · 1 comment
Open

Better error logging #34

chriskuech opened this issue Sep 15, 2019 · 1 comment
Labels
bug Something isn't working

Comments

@chriskuech
Copy link
Contributor

Current error reporting:
image

v1 behavior:

  • Error is captured and printed after the Requirements output
  • Exception callstack is printed with internal Requirements calls popped off.
@chriskuech chriskuech added the bug Something isn't working label Sep 15, 2019
@chriskuech
Copy link
Contributor Author

chriskuech commented Sep 20, 2019 •
edited

Can probably implement this in Invoke-Requirement by capturing the error in catch, then outputting the failure event, then throwing the error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chriskuech