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: error message of clientLogLevel #2021

Merged

Conversation

sottar
Copy link
Contributor

@sottar sottar commented Jun 12, 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?

Motivation / Use-Case

The error message of clientLogLevel is not correct, so fixed it.

ref. https://webpack.js.org/configuration/dev-server/#devserverclientloglevel

Breaking Changes

not breaking change

Additional Info

@jsf-clabot
Copy link

jsf-clabot commented Jun 12, 2019

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

@codecov
Copy link

codecov bot commented Jun 12, 2019

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2021   +/-   ##
=======================================
  Coverage   92.77%   92.77%           
=======================================
  Files          29       29           
  Lines        1149     1149           
  Branches      327      327           
=======================================
  Hits         1066     1066           
  Misses         79       79           
  Partials        4        4

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 303f4e9...3e336e2. Read the comment docs.

@hiroppy
Copy link
Member

hiroppy commented Jun 12, 2019

It has the reason(#1901 (comment)), but we've already had next branch, so I'll accept this change.

lib/options.json Outdated
@@ -389,7 +389,7 @@
"bonjour": "should be {Boolean} (https://webpack.js.org/configuration/dev-server/#devserverbonjour)",
"ca": "should be {String|Buffer}",
"cert": "should be {String|Buffer}",
"clientLogLevel": "should be {String} and equal to one of the allowed values\n\n [ 'info', 'warn', 'error', 'debug', 'trace', 'silent' ]\n\n (https://webpack.js.org/configuration/dev-server/#devserverclientloglevel)",
"clientLogLevel": "should be {String} and equal to one of the allowed values\n\n [ 'none', 'info', 'error', 'warning' ]\n\n (https://webpack.js.org/configuration/dev-server/#devserverclientloglevel)",
Copy link
Member

Choose a reason for hiding this comment

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

The description should have warn and silent, and we should update documentation.

- [ 'none', 'info', 'error', 'warning' ]
+ [ 'none', 'silent', 'info', 'error', 'warning', 'warn' ]

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thank you.
I tried warn and silent, but it doesn't work as well 🤔 Is it intended?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ah~~ it's my bad. The version of webpack-dev-server in my local is old. I'll fix it.
Then can I handle to update documentation?

Copy link
Member

@hiroppy hiroppy Jun 12, 2019

Choose a reason for hiding this comment

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

Oops, yep. I confused. none and warning are going to be deprecated at the next major version, instead of silent and warn.

Edit, ty

Copy link
Member

Choose a reason for hiding this comment

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

@sottar We've already had the updated documentation. So, I'll merge this documentation after merging this pr.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, I see. So the documentation is the latest right?
It seems different between you suggested above.

Copy link
Member

Choose a reason for hiding this comment

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

@hiroppy
Copy link
Member

hiroppy commented Jun 12, 2019

related documentation webpack/webpack.js.org#2976

Copy link
Member

@hiroppy hiroppy left a comment

Choose a reason for hiding this comment

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

Thanks, I'll update documentation on webpack/webpack.js.org#2976

@sottar
Copy link
Contributor Author

sottar commented Jun 12, 2019

@hiroppy Thank you~~ enjoy staying in Europe 😁

@alexander-akait alexander-akait merged commit c982836 into webpack:master Jun 13, 2019
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