I'd like to request that the plugin warn whenever it encounters a selector that it cannot test. I've been using this plugin for the last week and my team has been using it for longer than that, but it only occurred to us yesterday that the plugin doesn't do much unless @define comments are provided. I see that the person who opened #35 was confused about the same thing.
Perhaps an option like warnAboutUnknown could be supported that, if set to true, would raise a warning whenever it encounters a selector that does not match a provided @define comment. The warning would tip the developer off to the fact that the plugin can't test the named selector for BEM/SUIT compliance until a @define comment is provided.
Please correct me if I'm mistaken about something. Thank you! 🙂
Thanks for authoring this plugin.
I'd like to request that the plugin warn whenever it encounters a selector that it cannot test. I've been using this plugin for the last week and my team has been using it for longer than that, but it only occurred to us yesterday that the plugin doesn't do much unless
@definecomments are provided. I see that the person who opened #35 was confused about the same thing.Perhaps an option like
warnAboutUnknowncould be supported that, if set totrue, would raise a warning whenever it encounters a selector that does not match a provided@definecomment. The warning would tip the developer off to the fact that the plugin can't test the named selector for BEM/SUIT compliance until a@definecomment is provided.Please correct me if I'm mistaken about something. Thank you! 🙂