Skip to content

Fail the build when noEmitOnError is set and there's a type error #188

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

Merged
merged 5 commits into from
Apr 15, 2018

Conversation

dfreeman
Copy link
Member

fail

@dfreeman
Copy link
Member Author

@chriskrycho I didn't add anything to the README on this because I figured you may have thoughts on the best way to frame this as it relates to the overall effort of getting an app typechecking. Feel free to layer on any doc updates you've got to this branch, or give me a shout at some point and I can write something up.

@chriskrycho
Copy link
Member

SWEET. I'll write this up today. This is exactly what I was hoping we could do.

@chriskrycho
Copy link
Member

Pulled in a couple changes, will add more this afternoon. After that, I expect to merge and then cut a 1.3.0-beta.1 release.

@chriskrycho
Copy link
Member

…I think we somehow broke AppVeyor last night, @dfreeman. 😭

@chriskrycho
Copy link
Member

Oh! Ha. No: it just didn't trigger a new build because there's no change that it should build, but GitHub isn't realizing that.

@chriskrycho chriskrycho merged commit bee06ce into master Apr 15, 2018
@chriskrycho chriskrycho deleted the fail-the-build-but-on-purpose branch April 15, 2018 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants