oxlint-plugin-arch 0.6.1 → 0.6.3

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.6.3
+
+- Add a trailing comma when `object-multiline` splits an object, so the fix agrees with multiline comma rules.
+
+- Add opt-in `ternary-layout` and `call-arguments-multiline` layout rules with configurable thresholds and indentation. Presets remain unchanged.
+
+## 0.6.2
+
+- Export `oxlint-plugin-arch/rules/dillon-anti-slop` and `oxlint-plugin-arch/rules/module-policy` with TypeScript declarations. Resolve the preset's three first-party plugins through public package entry points, without changing rules or policy. Document standalone registration and third-party dependency ownership; verify built exports expose every supporting rule.
+
 ## 0.6.1
 
 - Relax the preset's shadcn defaults for stock composition, so strict consumers need no overrides: exact padding groups on `CardContent`/`PopoverContent`, gap and padding on `TabsContent`, and gap on `Tabs`/`HoverCardContent`/`SidebarHeader`/`BreadcrumbList`; exact `truncate` everywhere. Controls such as `Button` stay protected.

package/README.md

@@ -6,7 +6,7 @@ Keep a codebase shaped the way you designed it: files in the right folders, expo
 
 - 🗂️ **Filename-aware.** Rules derive expected names from the file they run on (`user-action.create.ts` → `makeUserActionCreate`).
 - 🎛️ **Configurable.** No app names, folders, or libraries are baked in. Globs and policy live in your config.
-- 🛟 **Safe autofix.** Layout and comment rules only touch whitespace or comments. Type-import fixes qualify scope-resolved references and skip unsafe rewrites.
+- 🛟 **Safe autofix.** Layout and comment rules touch whitespace or comments; `object-multiline` and `call-arguments-multiline` can also add trailing commas. Type-import fixes qualify scope-resolved references and skip unsafe rewrites.
 - ⚡ **Fast.** Built on Oxlint's JS plugin API and ESTree, with no extra parser.
 
 ---
@@ -264,6 +264,40 @@ export default defineConfig({
 })
 ```
 
+### Use the supporting plugins without the preset
+
+All three first-party rule sets have public package entry points. Register only the plugins and rules you need; this does not enable the preset or its policies.
+
+```ts
+import { defineConfig } from 'oxlint'
+
+export default defineConfig({
+  jsPlugins: [
+    { name: 'arch', specifier: 'oxlint-plugin-arch' },
+    { name: 'dillon-anti-slop', specifier: 'oxlint-plugin-arch/rules/dillon-anti-slop' },
+    { name: 'modules', specifier: 'oxlint-plugin-arch/rules/module-policy' },
+  ],
+  rules: {
+    'arch/no-literal-in': 'error',
+    'dillon-anti-slop/no-chained-type-assertions': 'error',
+    'modules/no-unknown': 'error',
+  },
+})
+```
+
+Both `/rules/` entry points also provide a default plugin export and TypeScript declarations. Do not import `dist/` paths. The preset resolves these same public entry points, including the existing package root for `arch`; it needs no other first-party plugin entry points. Individual rule implementations and helpers are bundled into those plugins.
+
+If you copy the preset's third-party plugin registrations into your own config, install those packages directly with `bun add -d` rather than relying on transitive dependency hoisting:
+
+| Scope | Packages |
+| --- | --- |
+| Always | `oxlint-plugin-eslint`, `eslint-plugin-import`, `@regru/eslint-plugin-prefer-early-return`, `eslint-plugin-unused-imports`, `eslint-plugin-perfectionist`, `eslint-plugin-tsdoc`, `@eslint-community/eslint-plugin-eslint-comments` |
+| Web roots | `eslint-plugin-react`, `eslint-plugin-react-you-might-not-need-an-effect`, `eslint-plugin-svg-jsx` |
+| CSS entry points with Tailwind enabled | `oxlint-tailwindcss` |
+| Same CSS scope with shadcn enabled | `@shadcn/lint` |
+
+These plugins remain **dependencies** of `oxlint-plugin-arch`, not peer dependencies: the preset loads its own installed copies. In an application-owned config, list directly used plugins as **devDependencies**. A reusable config package should use dependencies for plugins it resolves itself, or peerDependencies if it intentionally requires consumers to supply them. `@oxlint/plugins` is the bundled plugins' runtime dependency, not another preset rule set. `oxlint` remains a peer dependency; `oxlint-tsgolint` is an optional peer required when using the preset's type-aware checks. Native Oxlint plugin groups need no separate npm plugin packages.
+
 ## 🚀 Quick start
 
 Rules are switched on per folder with `overrides`. Here are three small ones:
@@ -393,7 +427,9 @@ Options that take one regex string (`pattern`, `allowPattern`, `forbid`, `requir
 | Rule | What it enforces |
 | --- | --- |
 | `padding-between-statements` 🔧 | Blank lines around functions and classes, around control flow, and before `return` in longer blocks; `multilineVariables: true` also separates multiline declarations, including exports (default `false`). |
-| `object-multiline` 🔧 | Objects with 3+ properties passed to a call go one property per line (`scope: 'all'` for every object). |
+| `object-multiline` 🔧 | Objects with 3+ properties passed to a call go one property per line with a trailing comma (`scope: 'all'` for every object). |
+| `ternary-layout` 🔧 | Join short conditionals or split long ones before `?` and `:`. [Details ↓](#ternary-layout) |
+| `call-arguments-multiline` 🔧 | Calls and constructors with 3+ arguments go one argument per line. [Details ↓](#call-arguments-multiline) |
 | `key-value-same-line` 🔧 | An object key and the start of its value stay on the same line. |
 | `chain-newline` 🔧 | Long method chains go one call per line. You pick which chains with `groups`. |
 | `call-array-multiline` 🔧 | Arrays passed to `Promise.all` (or callees you list) go one element per line. |
@@ -406,6 +442,18 @@ Options that take one regex string (`pattern`, `allowPattern`, `forbid`, `requir
 
 ## 🔍 Rule details
 
+### ternary-layout
+
+Options: `maxLength` (integer ≥ 1, default `160`) and `indent` (integer ≥ 1, default `2` spaces). The full resulting line, including its prefix and suffix, determines whether a conditional fits. Short multiline conditionals join; long single-line conditionals split before `?` and `:`, one indent deeper than their starting line. Direct template interpolations stay on one line regardless of length.
+
+Conditionals with a conditional parent or operand, comments inside, or multiline operands are skipped. Existing long multiline conditionals are left unchanged.
+
+### call-arguments-multiline
+
+Options: `minArguments` (integer ≥ 2, default `3`) and `indent` (integer ≥ 1, default `2` spaces). Calls and `new` expressions at the threshold put each argument and the closing `)` on separate lines. Arguments use one indent deeper than the line containing `(`. Fixes add a trailing comma, including after spread arguments.
+
+Calls already using separate lines for every argument and `)` are left unchanged, including their indentation and optional trailing comma. Calls containing comments, parenthesized arguments, or multiline arrow/function arguments are skipped. These are code fixes because they can add punctuation. Both new rules are opt-in and absent from presets.
+
 ### File size
 
 `limits.maxFileLines?: number` sets the existing ESLint `max-lines` ceiling on checked safety scopes; default `400`. Blank lines and comments remain skipped. Use native Oxlint overrides or the existing `ruleExclusions` configuration for deliberate per-file exceptions. File size is a ceiling, not a cohesion proof.