Hi guys,

Your plugin is great. I'm using it for my projects.

However, I think you should add this rule to the plugin: http://getbem.com/faq/#css-nested-elements

Thanks

Type of issue

• Bug report

Environment

• macOS Catalina 10.15.7
• darwin 19.6.0
• node 14.16.1
• npm 6.14.12

Expected behavior

linter would allow Placeholder Selects, e.g. %button { }

Current behavior

linter warns/errors with Rule expected but "%" found plugin/stylelint-bem-namics

Steps to reproduce the behavior

Run a placeholder selector through stylelint with the stylelint-bem plugin

%button {
  background-color: #000;
  color: #fff;
}

Enhancement to allow namespace to support a regular expression or array.

Context I am working with a project right now on a project that has too namespaces (i.e. mason and demo)

I would like to do be able to do something like

"namespace": "mason-|demo-"
OR
"namespace": ["mason-", "demo-"]

I am happy to submit a Pull Request if this idea is desired

Reproduce

      :deep(.ct-links) {
        &__list {
          display: block;
        }
      }

Comments

Is there a way I can get this Vue selector to work? See https://vuejs.org/api/sfc-css-features.html#scoped-css
It appears to error on the inner block.

My configuration is:

    'plugin/stylelint-bem-namics': {
      namespaces: [
        'ct-'
      ],
      patternPrefixes: [],
      helperPrefixes: []
    }

Hello !

Sorry, My english is not good.

When I use lessOptions.modifyVars, I want to add prefix at one classname, but get this error.

Can you help me ?

According to the BEM naming convention,
There are many styles of naming convention, not just 'contain no uppercase letters'
I am wondering are there some way to close the config of 'contain no uppercase letters'?

.mixin () {
}

Rule expected but "(" found plugin/stylelint-bem-namics

Hey,

it'd be super practical, if we'd split the code formatting config from the BEM naming config.
We don't use this package right now in e.g. React projects, where we use component based style loading and therefore don't need BEM.
However it would be great, if we included a default code formatting configuration, that provides default configurations for our CSS files.
I'd suggest to split this package into two separate ones: one for BEM and the other for basic CSS code formatting.

Is there any way to configure that?

BEM does not allow for nested elements, which this plugin does currently not complain about. It would be great to have this either changed or at least be configureable

Type of issue

• Feature request

With the current stylelint-bem, it's not possible to use an scss variable within a selector. This feature which exists for SCSS is quite handy to use within mixins to realize something like this:

@mixin some-mixin($selector) {
	/* stylelint-disable plugin/stylelint-bem-namics */
	#{$selector} {
            // your styles
        }
        /* stylelint-enable plugin/stylelint-bem-namics */
}

Could we consider to add this feature?

Type of issue

• Feature request

This plugin is using the getbem.com standard instead of the BEM standard from bem.info (which is from the original creators of BEM), it would nice if the customize the BEM conventions to match what we are targeting. Thanks.

https://en.bem.info/methodology/naming-convention/

Type of issue

• Bug report

Environment

• Node.js v16.14.2
• Mac OS 12.4
• NPM: 8.5.0
• Using postcss-scss as customSyntax

Expected behavior

When using a nested :is selector, no error should be thrown.

Current behavior

The fellowing error is thrown:

• Rule expected but ")" found plugin/stylelint-bem-namics

Steps to reproduce the behavior

Create an stylesheet with the fellowing CSS code:

.u-underline:is(:focus:not(.has-invisible-focus), :hover:not([disabled])) {
  text-decoration: underline;
}