@sinemacula/coding-standards 1.12.0 → 1.12.1

package/README.md

@@ -285,7 +285,6 @@ type-checked layer.
 | `@sinemacula/no-base-error` | Throw a domain-specific `Error` subclass, never the base `Error`; test code exempt. |
 | `@sinemacula/require-copyright` | Every file must carry a documentation comment with `@copyright` and `@author`. |
 | `@sinemacula/align-doc-tags` | `@author` and `@copyright` values line up at a single column; autofixable. |
-| `@sinemacula/pad-block-start` | An interface, class or enum body opens with a blank line; autofixable. |
 | `@sinemacula/single-line-property-doc` | A data member's documentation comment sits on one line; autofixable. |
 | `@sinemacula/multiline-function-doc` | A method's documentation comment spans multiple lines; autofixable. |
 
@@ -293,11 +292,10 @@ type-checked layer.
 to widen the accepted vocabulary from a consumer config. `max-methods-per-class` takes `max`, `no-base-error` takes
 `allow`, and `require-copyright` takes `tags` to adjust their defaults. `align-doc-tags` takes `tags` and `column`,
 the column counting from the `@`, so the default of 14 gives `@author` six spaces and `@copyright` three.
-`pad-block-start` governs the opening brace only, leaving the closing brace against the final member. Together
-`single-line-property-doc` and `multiline-function-doc` set a member's comment shape by its kind: data members
-(interface property signatures, enum members and data class fields) take one line, while methods, interface method
-signatures and class fields holding a function take several. A data comment is never required, only held to one line
-where present; a free function keeps the freedom of either shape.
+Together `single-line-property-doc` and `multiline-function-doc` set a member's comment shape by its kind: data
+members (interface property signatures, enum members and data class fields) take one line, while methods, interface
+method signatures and class fields holding a function take several. A data comment is never required, only held to
+one line where present; a free function keeps the freedom of either shape.
 
 The base layer also switches on a set of built-in rules: `@typescript-eslint/no-explicit-any`, `max-lines-per-function`
 (50 lines, test code exempt) and `max-depth` (4), plus `eslint-plugin-jsdoc` rules that require a documentation comment

package/js/eslint/index.js

@@ -50,7 +50,6 @@ export default [
             '@sinemacula/no-base-error': 'error',
             '@sinemacula/require-copyright': 'error',
             '@sinemacula/align-doc-tags': 'error',
-            '@sinemacula/pad-block-start': 'error',
             '@sinemacula/single-line-property-doc': 'error',
             '@sinemacula/multiline-function-doc': 'error',
 

package/js/eslint/plugin.js

@@ -5,7 +5,6 @@ import multilineFunctionDoc from './rules/multiline-function-doc.js';
 import noBaseError from './rules/no-base-error.js';
 import noInterfacePrefix from './rules/no-interface-prefix.js';
 import noMutableStatic from './rules/no-mutable-static.js';
-import padBlockStart from './rules/pad-block-start.js';
 import requireCopyright from './rules/require-copyright.js';
 import requireReadonlyPublicProperty from './rules/require-readonly-public-property.js';
 import singleLinePropertyDoc from './rules/single-line-property-doc.js';
@@ -35,7 +34,6 @@ export default {
         'no-base-error': noBaseError,
         'require-copyright': requireCopyright,
         'align-doc-tags': alignDocTags,
-        'pad-block-start': padBlockStart,
         'single-line-property-doc': singleLinePropertyDoc,
         'multiline-function-doc': multilineFunctionDoc,
     },

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@sinemacula/coding-standards",
-    "version": "1.12.0",
+    "version": "1.12.1",
     "description": "Centralized coding standards, static analysis configurations, and code quality tooling for all Sine Macula repositories.",
     "license": "Apache-2.0",
     "author": "Ben Carey <bdmc@sinemacula.co.uk>",

package/js/eslint/rules/pad-block-start.js

@@ -1,85 +0,0 @@
-import { createRule } from './lib.js';
-
-/** The member-carrying bodies whose first line is held clear of the brace. */
-const BODY_TYPES = new Set(['TSInterfaceBody', 'ClassBody', 'TSEnumBody']);
-
-/**
- * Require a blank line after the opening brace of an interface, class or enum
- * body.
- *
- * The first member then stands off from the declaration the way every later
- * member stands off from the one above it, so a body reads as an evenly spaced
- * list rather than crowding its opening line. Only the opening brace is
- * governed; the closing brace is left to sit against the final member.
- *
- * An empty body and a body written entirely on one line carry no member to
- * separate and are left alone. Where the first member opens with a
- * documentation comment the blank line falls above the comment, so the comment
- * stays attached to what it documents.
- *
- * @author      Ben Carey <bdmc@sinemacula.co.uk>
- * @copyright   2026 Sine Macula Limited
- */
-export default createRule({
-    name: 'pad-block-start',
-    meta: {
-        type: 'layout',
-        fixable: 'whitespace',
-        docs: {
-            description: 'Require a blank line after the opening brace of an interface, class or enum body.',
-        },
-        schema: [],
-        messages: {
-            missing: 'A body must begin with a blank line after its opening brace.',
-        },
-    },
-    defaultOptions: [],
-    create(context) {
-        const { sourceCode } = context;
-
-        /** Hold the first member of a body clear of the opening brace. */
-        function inspect(node) {
-            const brace = sourceCode.getFirstToken(node);
-            const close = sourceCode.getLastToken(node);
-
-            // A one-line body has no member to separate from the brace.
-            if (!brace || !close || brace.loc.end.line === close.loc.start.line) {
-                return;
-            }
-
-            const first = sourceCode.getTokenAfter(brace, { includeComments: true });
-
-            // An empty body carries nothing to stand off from the brace.
-            if (!first || first === close) {
-                return;
-            }
-
-            const blanks = first.loc.start.line - brace.loc.end.line - 1;
-
-            if (blanks === 1) {
-                return;
-            }
-
-            const onOwnLine = first.loc.start.line > brace.loc.end.line;
-
-            context.report({
-                loc: brace.loc,
-                messageId: 'missing',
-                fix: onOwnLine
-                    ? fixer => fixer.replaceTextRange(
-                        [brace.range[1], first.range[0]],
-                        `\n\n${' '.repeat(first.loc.start.column)}`,
-                    )
-                    : null,
-            });
-        }
-
-        const visitor = {};
-
-        for (const type of BODY_TYPES) {
-            visitor[type] = inspect;
-        }
-
-        return visitor;
-    },
-});