-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
feat: added the postprocessor
option
#518
Conversation
@@ -8,6 +8,7 @@ logs | |||
*.log | |||
npm-debug.log* | |||
.eslintcache | |||
.cspellcache |
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.
We can also disable cache in cpsell. It doesn't differ much from no-cache
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.
It has a big changes when you have a lot of files, I don't think we need disable it, we use cache everywhere
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.
ok
test/postprocessor-option.test.js
Outdated
expect(getErrors(stats)).toMatchSnapshot("errors"); | ||
}); | ||
|
||
it('should work with Async "postprocessor" Function option', async () => { |
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.
it('should work with Async "postprocessor" Function option', async () => { | |
it('should work with async "postprocessor" function option', async () => { |
This PR contains a:
Motivation / Use-Case
fixes #291
Breaking Changes
No
Additional Info
No