You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an opportunity to DRY up a bit of code that's in ./lib/utils.js, specifically for exports.etag and exports.wetag. Drying up the code would NOT change the API.
The text was updated successfully, but these errors were encountered:
lpage
added a commit
to lpage/express
that referenced
this issue
May 18, 2017
Please, there is no need to file an issue immediately before filing a PR, especially for a non-issue. If there is any conversation, it ends up split between two locations and also creates extra items to track, close, respond to. Thanks!
lpage
added a commit
to lpage/express
that referenced
this issue
May 18, 2017
On Thu, May 18, 2017 at 11:22 AM, Douglas Wilson ***@***.***> wrote:
Please, there is no need to file an issue immediately before filing a PR,
especially for a non-issue. If there is any conversation, it ends up split
between two locations and also creates extra items to track, close, respond
to. Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3313 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABcpUP0mw7xI_lYXfCh5POZw5AIP3oJaks5r7IxJgaJpZM4NfmCt>
.
lpage
added a commit
to lpage/express
that referenced
this issue
May 18, 2017
There is an opportunity to DRY up a bit of code that's in ./lib/utils.js, specifically for exports.etag and exports.wetag. Drying up the code would NOT change the API.
The text was updated successfully, but these errors were encountered: