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

fix maxWarnings when multiple reports #160

Merged

Conversation

kevsul
Copy link
Contributor

@kevsul kevsul commented Sep 19, 2019

Fixes #159

@coveralls
Copy link

coveralls commented Sep 19, 2019

Coverage Status

Coverage remained the same at ?% when pulling bfea9e4 on kevsul:fix-maxWarnings-when-multiple-reports into 835b127 on protofire:master.

@fvictorio
Copy link
Contributor

Wow, huge bug. Thanks @kevsul! Could you please run prettier so that the CI passes?

@pablofullana
Copy link
Contributor

Looks like something that could have been caught by a test taking into multiple reports into account. @fvictorio can we plan on adding this scenario?

@kevsul
Copy link
Contributor Author

kevsul commented Sep 19, 2019

Wow, huge bug. Thanks @kevsul! Could you please run prettier so that the CI passes?

Done.

@fvictorio fvictorio merged commit 3c738a3 into protofire:master Sep 19, 2019
@fvictorio
Copy link
Contributor

Thanks @kevsul!

@pablofullana: I opened #161 to track this.

@kevsul kevsul deleted the fix-maxWarnings-when-multiple-reports branch September 20, 2019 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

maxWarnings flag doesn't work as expected when there are multiple source files
4 participants