Closed jrwebdev closed 7 years ago
Failing tests seem unrelated to my change - it appears to be the use of null
instead of undefined
in the last test. Let me know if you'd like me to change that as I don't really know much about Stylelint.
@jrwebdev: Are you interested in taking over maintenance of this plugin? I do not use it currently, so it would be better off in the hands of an active user.
implicitComponents
doesn't have to be an array, it can be just a string too.
@davidtheclark I'm probably not the best person to pick this up as I'm not too familiar with Stylelint and I was just evaluating it for my company for now. But if we do pick it up I could maybe take it on.
@jackwilsdon this perhaps highlights the above point of me not knowing it too well - I assumed that the array would validate one of _.isBoolean
, _.isString
or the function for testing for an array of strings. Seemed to work fine when I manually tested it but I'll take another look.
Oops, I missed the bit where you passed _.isString
! Sorry! 😆 😜
@jrwebdev: This PR looks fine to me. Can you please try merging in the latest version of master? I'm hoping that will fix this test failure you're seeing.
Hi gents, this pull request looks ready to go. I'd be keen to see it merged :)
Published in 1.1.0. Thanks @jackwilsdon!
Awesome guys, thanks!
Added support for the
implicitComponents
option as detailed here:https://github.com/postcss/postcss-bem-linter#define-components-and-utilities-implicitly-based-on-their-filename