-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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: add null check for connection.headers #2200
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2200 +/- ##
=======================================
Coverage 93.91% 93.91%
=======================================
Files 34 34
Lines 1282 1282
Branches 370 371 +1
=======================================
Hits 1204 1204
Misses 71 71
Partials 7 7
Continue to review full report at Codecov.
|
d602201
to
1d05d6c
Compare
/cc @Loonride |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need tests
If the connection object is null, there is no use in passing it along to the callback since we can't do anything with it. I think it is better off being:
|
I thought about this. As you have a check in webpack-dev-server/lib/Server.js Lines 662 to 672 in a355894
I want to reuse. |
I added |
Any updates? |
Understood. I have added some notes on the tests. |
Looks good to me /cc @evilebottnawi @hiroppy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/cc @hiroppy
When will you guys do the npm publish? |
@wood1986 not yet I guess, you can use the master branch on your
|
fix #2199
For Bugs and Features; did you add new tests?
Motivation / Use-Case
Breaking Changes
Additional Info