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.

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

BREAKING: File not found is an Error, not a Warning #247

Merged
merged 1 commit into from
Nov 17, 2016
Merged

Conversation

RyanZim
Copy link
Collaborator

@RyanZim RyanZim commented Nov 17, 2016

Fixes #192.

@MoOx What do you think of this? Is there some other case that we can test for a readable stack trace, since file not found is now an error?

@RyanZim RyanZim added this to the v9.0.0 milestone Nov 17, 2016
Copy link
Contributor

@MoOx MoOx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm this way

@RyanZim RyanZim merged commit 3352a37 into v9-dev Nov 17, 2016
@RyanZim RyanZim deleted the error branch November 17, 2016 20:58
@RyanZim
Copy link
Collaborator Author

RyanZim commented Nov 17, 2016

@MoOx Any ideas on if/what we should use for testing for a readable stack trace, since I removed the old test?

@MoOx
Copy link
Contributor

MoOx commented Nov 17, 2016

you can check error.stack, error.message etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants