![]() Patterns are applied against the file path relative to the directory of the config file. The customSyntax property will be replaced, whereas plugins, extends, rules, etc. should contain at least one other regular configuration property, such as customSyntax, rules, extends, etc.must contain a files property, which is an array of glob patterns that specify which files the configuration should be applied to.The value of the overrides property is an array of objects. Look at the plugin's documentation to know what the rule name should be. ![]() Once the plugin is declared, within your "rules" object you'll need to add options for the plugin's rule(s), just like any standard rule. path relative to the invoking configuration file.As with extends, above, a "locater" can be either a: To use a plugin directly, add a "plugins" array to your config, containing either plugin objects or "locaters" identifying the plugins you want to use. For example, the stylelint-config-standard-scss config includes the stylelint-scss plugin. Plugins are often included within shared configs that you can extend. Plugins are custom rules or sets of custom rules built to support methodologies, toolsets, non-standard CSS features, or very specific use cases.įor example, stylelint-order is a popular plugin pack to order things like properties within declaration blocks. You'll find more configs in Awesome Stylelint. if configA has extends: "./configB", we'll look for configB relative to configA). json extension, relative to the referencing configuration (e.g. ![]()
0 Comments
Leave a Reply. |