Uh oh!
There was an error while loading. Please reload this page.
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
1d05d6cComparealexander-akait
commented
Aug 16, 2019
/cc @Loonride |
knagaitsev
commented
Aug 16, 2019
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: |
wood1986
commented
Aug 17, 2019
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. |
wood1986
commented
Aug 17, 2019
I added |
wood1986
commented
Aug 19, 2019
Any updates? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
knagaitsev
commented
Aug 20, 2019
Understood. I have added some notes on the tests. |
Uh oh!
There was an error while loading. Please reload this page.
knagaitsev
commented
Aug 20, 2019
Looks good to me /cc @evilebottnawi@hiroppy |
wood1986
commented
Aug 21, 2019
When will you guys do the npm publish? |
Sleepful
commented
Aug 26, 2019
@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