Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"%s" is not supported in the .stylelintrc.json file in a custom message #6407

Closed
szulcus opened this issue Oct 13, 2022 · 2 comments
Closed

Comments

@szulcus
Copy link

szulcus commented Oct 13, 2022

What steps are needed to reproduce the bug?

I am using Nuxt 3 (3.0.0-rc.8) with vite-plugin-stylelint package (^1.8.1) and extension for VS Code (https://marketplace.visualstudio.com/items?itemName=stylelint.vscode-stylelint) , v1.2.3). I temporarily do not have time to reproduce this bug, but if necessary I can try to create one in the next few days.

What Stylelint configuration is needed to reproduce the bug?

{
	"extends": [
		"stylelint-config-standard-scss",
		"stylelint-config-recommended-vue/scss",
		"stylelint-config-idiomatic-order"
	],
	"rules": {
		"selector-class-pattern": ["^(?:(?:o|c|u|t|s|is|has|_|js|qa)-)?[a-zA-Z0-9]+(?:-[a-zA-Z0-9]+)*(?:__[a-zA-Z0-9]+(?:-[a-zA-Z0-9]+)*)?(?:--[a-zA-Z0-9]+(?:-[a-zA-Z0-9]+)*)?(?:\\[.+\\])?$", {
			"message": "Expected class selector \"%s\" to be compatible with BEM methodology"
		}],
	}
}

How did you run Stylelint?

With vite-plugin-stylelint package.

Which version of Stylelint are you using?

^14.13.0

What did you expect to happen?

Get the class name instead of the "%s".

What actually happened?

I get the "%s":
image

Does the bug relate to non-standard syntax?

No response

Proposal to fix the bug

No response

@ybiquitous
Copy link
Member

@szulcus Thanks for writing the report and for using the template. We can confirm the bug on the demo.

We've fixed the bug via PR #6391 already. Please be patient for the next release.

You can also use the HEAD version to confirm the fixed bug via npm install stylelint/stylelint.

@ybiquitous ybiquitous closed this as not planned Won't fix, can't repro, duplicate, stale Oct 13, 2022
@szulcus
Copy link
Author

szulcus commented Oct 13, 2022

@ybiquitous Thanks a lot! ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants