Uh oh!
There was an error while loading. Please reload this page.
Added support for brotli ('br') content-encoding - #403
Conversation
2015f22 to
5c8d15fCompare
dougwilson
left a comment
There was a problem hiding this comment.
The docs need to be updated to add the new encoding that is inflated and explain how the users know if it will be available or not.
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.
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.
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.
Uh oh!
There was an error while loading. Please reload this page.
8a297bb to
a6dd921Compare| ways, for example the `foo` property may not be there or may not be a string, | ||
| and `toString` may not be a function and instead a string or other user input. | ||
| **Note** Brotli provides better and faster compression then gzip or deflate, but is supported only since Node.js versions v11.7.0 and v10.16.0. |
There was a problem hiding this comment.
Please hard-wrap this line to match the width of the rest of the lines. In addition, since this module only ever decompresses, is this note about compression relevant? I would think that the information about version support should be along with the br support docs, otherwise users may not see it.
There was a problem hiding this comment.
Please stop marking this as resolved when you didn't address all my comments or respond back with why you don't think you should address some part to have a discussion on it.
There was a problem hiding this comment.
I did hard wrap this when resolving the original comment, and now this line does not even exist 😂
This is why it was hidden. It's marked as "outdated" automatically
There was a problem hiding this comment.
I would think that the information about version support should be along with the br support docs, otherwise users may not see it.
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.
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.
b995bfe to
6c80c9eCompareUh 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.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
danielgindi
commented
Jul 11, 2020
@dougwilson Are we good to go? ;-) |
dougwilson
commented
Jul 11, 2020
No, it seems like since you keep force pushing it is closing out unresolved comments I made. Please make sure you have responded to all my outstanding requests and don't resolve them before you do or without commenting on them first :) |
dougwilson
commented
Jul 11, 2020
I just tried to unresolve a few but they still do not show. I will plan to re-review and remake those comments again next week. Have a good weekend. |
danielgindi
commented
Jul 11, 2020
I remember resolving them all, but please add any outstanding comments... |
dougwilson
commented
Jul 11, 2020
I was just able to get at least one of the unresolved ones to re-show up as unresolved again above. |
danielgindi
commented
Jul 13, 2020
I addressed them all now. Improved the docs a bit. |
dougwilson
left a comment
There was a problem hiding this comment.
There is still an unresolved comment.
danielgindi
commented
Jul 13, 2020
It shows me that you "requested changes" but does not show any changes that were requested! |
dougwilson
commented
Jul 13, 2020
Hm, weird. Here is a link to it: #403 (comment) |
dougwilson
commented
Jul 13, 2020
It is clear this PR is quite a mess at this point, and things are getting resolved that are not resolved. Please open this PR again so we can restart the review process 🙏 |
dougwilson
commented
Jul 13, 2020
Edit: to clarify, I closed this because it seems like the comments are getting resolved likely automatically, and so it's hard to keep track of what is and is not resolved at this point. I think a fresh PR and a new review with this current iteration of code would help a lot in getting this landed is all. If there was a way in GitHub for me to just erase all comments above or something to "reset" a PR that would be awesome, but unfortunately there is no such feature... :( |
danielgindi
commented
Jul 13, 2020
Okay, made a new one. |

expressjs/compression#172
https://medium.com/oyotech/how-brotli-compression-gave-us-37-latency-improvement-14d41e50fee4
https://caniuse.com/#feat=brotli