Richard Hallows

With the semantic versioning change in `8.0.0`, I think this can be done in an `8.x`. @evilebottnawi Feel free to get it in `8.0.0`, but I don't think it's a...

It's fantastic that you're rolling out stylelint and you're finding it helpful. (As an aside, your recent work on the experimental PostCSS tokenizer is very exciting and could be immensely...

Removed stylistic rules from task list (see https://github.com/stylelint/stylelint/issues/5674). Two remain: - `selector-pseudo-class-disallowed-list` - `selector-pseudo-class-allowed-list`

Thanks for the detailed report and for using the template. I can reproduce the throw using [the demo](https://stylelint.io/demo#N4Igxg9gJgpiBcIBUAfAzgBwIYDsAEwAvgDo6moCuOA1jhAO75GkgA0IaAnjgC5YAeCcGjRtwEHADMAlgHMhwUnjzEQAJwoAbGGlXwCS5So4xtYHhDUBaHpwwwrdK1VoMyCPAG1DRvDw0wrD5Givi+RqpydGowACp2OnpexgD0SCmqeAC6wcokYco5YfmEIIRAA). I believe the parse error is due to the `*` in the...

To allow the following: ```css * {} *|* {} *|foo {} ``` You can use: ```json { "rules": { "selector-type-no-unknown": [ true, { "ignoreTypes": [ "foo" ] } ] }...

> Thanks for the detailed answer No worries. I'd like to wrap my head around it, even if it is a fringe issue. > > As * is parsed as...

Thanks for the detailed write-up! I feel I have a better grasp of namespaces now. The good news is that the rule already does most of what you described. An...

I can't remember the historical reasons why we ended up with `.stylelintignore`, `ignoreFiles` and `--ignore-pattern`. Consolidating to a single mechanism SGTM, i.e. `ignorePatterns: []` -> `.stylelintignore` -> `--ignore-pattern` (with each...

Thanks for the report. Labelling as ready to implement.

> @jeddy3 I verified this and indeed happens with both 13.7.2 and 13.8.0. Thanks! It looks to be a longer-standing bug than a regression with 13.8.0. I've labelled the issue...