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: update clientLogLevel to match docs and error #1825

Merged
merged 1 commit into from
Apr 27, 2019
Merged

fix: update clientLogLevel to match docs and error #1825

merged 1 commit into from
Apr 27, 2019

Conversation

gabemeola
Copy link
Contributor

@gabemeola gabemeola commented Apr 26, 2019

  • This is a bugfix
  • This is a feature
  • This is a code refactor
  • This is a test update
  • This is a docs update
  • This is a metadata update

For Bugs and Features; did you add new tests?

Yes

Motivation / Use-Case

The clientLogLevel implementation was incorrect with the documentation.
https://webpack.js.org/configuration/dev-server/#devserverclientloglevel
This PR brings it up to date.

Currently if you use trace, debug, warn, or silent or will receive a cli incorrect param error.
Screen Shot 2019-04-26 at 12 38 42 PM

Breaking Changes

This will cause a cli error for users using "clientLogLevel": "warning | none".
The correct property should be "warn" or "silent".

@jsf-clabot
Copy link

jsf-clabot commented Apr 26, 2019

CLA assistant check
All committers have signed the CLA.

@alexander-akait
Copy link
Member

Please fix ci problems, looks we need update snapshots

@gabemeola
Copy link
Contributor Author

Please fix ci problems, looks we need update snapshots

Updated. Found a few other places the docs needed to be updated and changed as well.

@codecov
Copy link

codecov bot commented Apr 27, 2019

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #1825   +/-   ##
=======================================
  Coverage   89.47%   89.47%           
=======================================
  Files           9        9           
  Lines         608      608           
  Branches      185      185           
=======================================
  Hits          544      544           
  Misses         54       54           
  Partials       10       10

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 b5bc05c...14e8f7c. Read the comment docs.

@hiroppy
Copy link
Member

hiroppy commented Apr 27, 2019

@gabemeola
Copy link
Contributor Author

@hiroppy For sure. Sent a pr webpack/webpack.js.org#2976

@hiroppy
Copy link
Member

hiroppy commented Apr 27, 2019

Thanks!

hubgit added a commit to hubgit/docz that referenced this pull request May 17, 2019
As of [v3.4.0](https://github.com/webpack/webpack-dev-server/releases/tag/v3.4.0) the option "none" is no longer a valid value for webpack-dev-server's clientLogLevel config.

webpack/webpack-dev-server#1825
@hubgit
Copy link

hubgit commented May 17, 2019

This is going to be a breaking change for quite a few projects - might it be better to continue supporting "none" and "warning" as synonyms for "silent" and "warn"?

@hiroppy
Copy link
Member

hiroppy commented May 17, 2019

hmm... according to the output, this pr is correct. but also I can understand what you are saying. /cc @evilebottnawi

@alexander-akait
Copy link
Member

@hubgit yes you are right, can you open issue, it is breaking change and regression

@hubgit
Copy link

hubgit commented May 17, 2019

Created #1899

@alexander-akait
Copy link
Member

@hubgit thanks

hiroppy added a commit that referenced this pull request May 17, 2019
hiroppy added a commit that referenced this pull request May 17, 2019
swyxio pushed a commit to doczjs/docz that referenced this pull request May 17, 2019
As of [v3.4.0](https://github.com/webpack/webpack-dev-server/releases/tag/v3.4.0) the option "none" is no longer a valid value for webpack-dev-server's clientLogLevel config.

webpack/webpack-dev-server#1825
@baoduy
Copy link

baoduy commented May 20, 2019

Hope this fix will be released soon as I'm also facing the same issue now

@hiroppy
Copy link
Member

hiroppy commented May 20, 2019

This issue has already fixed and v3.4.1 has already released.

EugeneHlushko pushed a commit to webpack/webpack.js.org that referenced this pull request Jun 12, 2019
* fix(docs): update clientLogLevel options

From webpack/webpack-dev-server#1825

* Changed `none` to `silent`
* Changed `warning` to `warn`
* Added `trace` and `debug

* docs(dev-server): add `none` and `warning` to clientLogLevel
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.

6 participants