-
-
Notifications
You must be signed in to change notification settings - Fork 73
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
StyleLint plugin should work without configuration and just use default one #33
Conversation
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.
Thanks for the PR! TBH I think the good reason for requiring the config is to make sure your .stylelintrc
file is picked up.
I suppose we could allow you to just pass in the path to your .stylelintrc
as the only option and then just use the defaults for the rest. What do you think?
|
||
return pack(assign({}, baseConfig, config)) | ||
.then(function (stats) { | ||
expect(stats.compilation.errors).to.have.length(0); |
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.
Could you add the assertion for the stats.compilation.warnings
as well (since the test title implies it)?
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.
sure
I don't think we should requiring config, default one works great. Same as eslint |
@vieron I've had some time to think about this properly and I think it's a good idea. Do you have any objections? If not I'll release this as the next version :) |
* It should work without configuration, just use default one * It should warn user if .stylelintrc file does not exit * Add warnings check
Currently it throws exception for this config:
This is fix for this use case