Richard Hallows

> Suggestions for types of messages to return would be very welcome The [only convention](https://github.com/stylelint/stylelint/blob/master/docs/developer-guide/rules.md#determine-warning-messages) we have in stylelint is that messages either start with "Expected" or "Unexpected". Your examples...

Agreed. Sounds great! We were anticipating the stylelint plugin being called `stylelint-declaration-no-valid`. The plugin might need to detect non-standard syntax (variable interpolations, dollar variables etc) and ignore declarations that contains...

> @jeddy3 Did you mean `stylelint-declaration-no-invalid`? Ha, yes I did :) > but it might be worth adding support still as long as this behaviour was opt-in. That facilitates this...

We only recently added the capability for plugins to include optional metadata and none of the ones listed above uses it, including the stylelint-scss plugin pack. However, I locally tested...

> We only recently added the capability for plugins to include optional metadata and none of the ones listed above uses it, including the stylelint-scss plugin pack. My bad. I...

@Reda011 Resolved in latest version of the VS Code extension: https://github.com/stylelint/vscode-stylelint/pull/416

We [already expose the globby options object to the Node.js API](https://stylelint.io/user-guide/usage/node-api#globbyoptions). Can you make it available to the CLI too? For example: ``` stylelint '**/*.css' --globby-options "dot: false" ``` It'll...

Let's an `--globby-options` flag. > I could potentially help... Who's going to be in charge of this implementation? How does it work? It's great you want to help as a...

> This would be much more helpful for users: Agreed. I'll label the issue as ready to go. @IAMtheIAM Please consider [contributing](https://stylelint.io/contributing) these changes if you have time.

@cmalard Thanks for the report and for using the template. @evilebottnawi Has correctly label this as "help wanted". Feel free to dig and contribute a PR if you'd like to...