persona-community-5/.pnpm-store/v3/files/03/e48601d559227020f7f08ee602327941d489cf7d21ed392173083415a3181e47e88241abf14ef6e6517818692a56f7bc0d151c03cafb0f90da240f5ade6dfd
rdev-worker a1d0d1bf1c
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
build: /implement-feature community-ui --requirements 'Build the React commu...
2026-02-24 08:22:30 +00:00

37 lines
1.1 KiB
Plaintext

---
description: 'Require or disallow padding lines between statements.'
---
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
> 🛑 This file is source code, not the primary documentation location! 🛑
>
> See **https://typescript-eslint.io/rules/padding-line-between-statements** for documentation.
This rule extends the base [`eslint/padding-line-between-statements`](https://eslint.org/docs/rules/padding-line-between-statements) rule.
It adds support for TypeScript constructs such as `interface` and `type`.
## Options
In addition to options provided by ESLint, `interface` and `type` can be used as statement types.
For example, to add blank lines before interfaces and type definitions:
```jsonc
{
// Example - Add blank lines before interface and type definitions.
"padding-line-between-statements": "off",
"@typescript-eslint/padding-line-between-statements": [
"error",
{
"blankLine": "always",
"prev": "*",
"next": ["interface", "type"],
},
],
}
```
**Note:** ESLint `cjs-export` and `cjs-import` statement types are renamed to `exports` and `require` respectively.