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: default(.json -> .js). Disable css usage audit #1911
Conversation
this now becomes a disabled audit, though we're keeping it in the source tree for good reasons. I wonder if theres somewhere else we can clearly indicate it's disabled, as unfortunately commenting out in the default.json isn't a possibility. how about also changing the audit.meta.name from |
Time to |
YUP. patrick wants to, too. let's do it. |
BOOM! 💥
wait, @paulirish changing default.js is not compatible with that plan... |
i'll cut a separate PR for 1.6.0 branch? |
This reverts commit 8922e25.
PTAL for added json -> js :) |
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.
LGTM, though maybe we'd want to drop the .js
in the require()
calls while in here so it doesn't matter what the file extension is?
oh, oops, I literally just merged :) makes it easy to find files requires with grep/simple search though so i'm actually not as jazzed about extension-less requires |
fair (though I just saved a regex for that :). Main benefit is that it makes it transparent where the data is coming from (json or from executed code), but since this is the hardcoded default config it doesn't matter |
Main benefit is that it makes it transparent where the data is coming from
You mean opaque? ;) haha, that's exactly why I don't like it!
…On Mon, Mar 27, 2017 at 5:36 PM, Brendan Kenny ***@***.***> wrote:
fair (though I just saved a regex for that :). Main benefit is that it
makes it transparent where the data is coming from (json or from executed
code), but since this is the hardcoded default config it doesn't matter
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1911 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACMdEnHtYvU783aUyOV9FuB8LlVA_2LOks5rqFYNgaJpZM4MqoWY>
.
|
Breaking changes have landed in protocol (currently failing all AppVeyor builds) and we're punting on fixing the accuracy until after IO anyway, just disable for now.