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

Do not show warnings @ 'overlay' unless explicitly set #881

Merged

Conversation

dcarral
Copy link
Contributor

@dcarral dcarral commented Apr 22, 2017

This change tweaks the feature behavior (implemented @ #790), so it matches the intended behavior (described @ #789):

overlay: true would be the same as overlay: { errors: true, warnings: false }.

This PR would supersede survivejs/webpack-book#262.


Did you add or update the examples/?

It wasn't needed, since the current example explicitly forces warnings to be shown/captured.

Does this PR introduce a breaking change?

Projects using the overlay: true option would stop showing warnings, unless their Webpack config gets updated to explicitly show them.

This change tweaks the feature behavior (implemented @ webpack#790),
so it matches the intended behavior (described @ webpack#789).

This PR would supersede survivejs/webpack-book#262.
@jsf-clabot
Copy link

jsf-clabot commented Apr 22, 2017

CLA assistant check
All committers have signed the CLA.

@codecov
Copy link

codecov bot commented Apr 22, 2017

Codecov Report

Merging #881 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #881   +/-   ##
=======================================
  Coverage   72.13%   72.13%           
=======================================
  Files           4        4           
  Lines         463      463           
  Branches      139      139           
=======================================
  Hits          334      334           
  Misses        129      129

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7fdb06...ca3ca2a. Read the comment docs.

@jamieathans
Copy link

Is it possible for this PR to be merged and a new webpack-dev-server bug-fix release be push to npm ASAP?

I ask because this issue/behaviour is affecting projects built with the latest version of the angular-cli - 1.0.1 (angular-cli projects hard-code overlay:true in development mode).

@shellscape shellscape merged commit e5b6202 into webpack:master Jul 10, 2017
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.

None yet

4 participants