This rule will help you reduce the number of Tailwind CSS classnames by using shorthands.
Examples of incorrect code for this rule:
<div class="border-t-4 border-r-4 border-b-4 border-l-4">border shorthand</div>Examples of correct code for this rule:
<div class="border-4">border shorthand</div>At the moment, the rule will not merge mixed classnames (e.g. using regular values AND arbitrary values).
<div class="border-t-[0] border-r-0 border-b-0 border-l-[0]">
won't be converted to border-0 shorthand
</div>Also, unless you are using the classnames-order rule, the order of your classnames may be affected by the fix.
If indeed, you are using the classnames-order rule, then it'll be automatically re-ordered during the next lint process (depending on your autofix preferences) and you won't notice any order issue.
...
"tailwindcss/enforces-shorthand": [<enabled>, {
"callees": Array<string>,
"config": <string>|<object>,
"tags": Array<string>,
}]
...If you use some utility library like @netlify/classnames-template-literals, you can add its name to the list to make sure it gets parsed by this rule.
For best results, gather the declarative classnames together, avoid mixing conditional classnames in between, move them at the end.
By default the plugin will try to load the file tailwind.config.js at the root of your project.
This allows the plugin to use your customized colors, spacing, screens...
You can provide another path or filename for your Tailwind CSS config file like "config/tailwind.js".
If the external file cannot be loaded (e.g. incorrect path or deleted file), an empty object {} will be used instead.
It is also possible to directly inject a configuration as plain object like { prefix: "tw-", theme: { ... } }.
Finally, the plugin will merge the provided configuration with Tailwind CSS's default configuration.
Optional, if you are using tagged templates, you should provide the tags in this array.
This rule will fix the issue for you.