@plumeria/eslint-plugin 18.2.15 → 18.2.17

package/README.md

@@ -64,7 +64,10 @@ A single rule can override that if you need it to:
 The name must match whatever the loader or unplugin was given. If they disagree,
 the lint rules report against a prop the compiler never transforms.
 
-## Rules
+## Recommended rules
+
+The following rules are enabled by `plumeria.configs.recommended` with the
+severity shown in [Recommended configuration](#recommended-configuration).
 
 ### props-require-import
 
@@ -118,6 +121,50 @@ properties in a vertical one, which is per element and cannot be read from the
 source. The rule reads them as one property; disable the line where an element
 is known to be vertical.
 
+### no-unknown-css-properties
+
+Disallow unknown CSS properties in camelCase within `css.create`, `css.keyframes`, and `css.viewTransition`.
+
+### no-unused-keys
+
+Warns when object keys are defined but not used, mainly in component files.
+
+### sort-properties
+
+Automatically sorts CSS properties in the recommended order for consistency and maintainability.
+
+### format-properties
+
+Automatically format for consistency and maintainability.
+
+- Formats a line into a multi-line.
+- Formats by filling in blank lines.
+
+### validate-values
+
+Validates CSS property values for correctness. Only standard CSS properties are checked; properties with string literal keys (e.g., computed or dynamic property names) are not validated.
+
+### validate-pseudos
+
+Validates CSS pseudo-classes and pseudo-elements inside `css.create()`. It checks for typos and structural correctness and supports validation of computed keys when TypeScript is available.
+
+## Optional rules
+
+These rules are not enabled by `plumeria.configs.recommended`. Enable only the
+policy or transformation that fits the project:
+
+```js
+export default [
+  plumeria.configs.recommended,
+  {
+    rules: {
+      '@plumeria/no-physical-properties': 'warn',
+      '@plumeria/expand-border-shorthands': 'warn',
+    },
+  },
+];
+```
+
 ### expand-border-shorthands
 
 Expands a border shorthand that bundles a width, a style and a color —
@@ -128,7 +175,7 @@ them turns the last unrankable pairs into ordinary shorthand-to-longhand ones.
 
 Fixable. A value it cannot split, such as `var(--edge)` or `inherit`, is
 reported without a fix: leaving it silent would let the expanded declarations
-elsewhere outrank it. Not part of `recommended`.
+elsewhere outrank it.
 
 ```js
 borderTop: '1px solid red'
@@ -149,38 +196,11 @@ Accepts `{ sizes }`, which adds `width`, `height`, their `min`/`max` forms,
 default: a size is one property under either spelling, while an edge is what a
 direction reverses.
 
-Neither is part of `recommended`, and turning both on is contradictory. Reach
-for one when you want the pairs `no-order-dependent-overlap` reports to be
-impossible to write: a property that appears under one spelling only can never
-meet its other spelling on an element. A shorthand with no single counterpart,
-such as `borderBlockWidth`, is outside either rule and stays reported.
-
-### no-unknown-css-properties
-
-Disallow unknown CSS properties in camelCase within `css.create`, `css.keyframes`, and `css.viewTransition`.
-
-### no-unused-keys
-
-Warns when object keys are defined but not used, mainly in component files.
-
-### sort-properties
-
-Automatically sorts CSS properties in the recommended order for consistency and maintainability.
-
-### format-properties
-
-Automatically format for consistency and maintainability.
-
-- Formats a line into a multi-line.
-- Formats by filling in blank lines.
-
-### validate-values
-
-Validates CSS property values for correctness. Only standard CSS properties are checked; properties with string literal keys (e.g., computed or dynamic property names) are not validated.
-
-### validate-pseudos
-
-Validates CSS pseudo-classes and pseudo-elements inside `css.create()`. It checks for typos and structural correctness and supports validation of computed keys when TypeScript is available.
+Turning both rules on is contradictory. Reach for one when you want the pairs
+`no-order-dependent-overlap` reports to be impossible to write: a property that
+appears under one spelling only can never meet its other spelling on an element.
+A shorthand with no single counterpart, such as `borderBlockWidth`, is outside
+either rule and stays reported.
 
 ## CLI (plumerialint)
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@plumeria/eslint-plugin",
-  "version": "18.2.15",
+  "version": "18.2.17",
   "description": "Plumeria ESLint plugin",
   "author": "Refirst 11",
   "license": "MIT",