🐞 BUG: `padding-line-between-statements` & `lines-around-comment` rules conflict with each other

Environment

Node version: v16.5 npm version: - Local ESLint version: v7.32 Global ESLint version: Same Operating System: Linux

What parser are you using?

Default (Espree)

What did you do?

Config

'padding-line-between-statements' : [
	// Disallow empty lines between consecutive variable declarations
	{
		blankLine : 'never',
		prev      : [
			'singleline-let',
			'singleline-const',
			'singleline-var',
		],
		next      : [
			'singleline-let',
			'singleline-const',
			'singleline-var',
		],
	},
]

// Require empty line before comments
'lines-around-comment' : [
	{
		beforeBlockComment         : true,
		beforeLineComment          : true,
		applyDefaultIgnorePatterns : false,
	},
],

Example

// Works
const apple = 'Apple'
const cat   = 'Cat'

// Produces lint errors when there is a space between these two declarations & also when, there is none.

// Fruit
const apple = 'Apple'

// Animal
const cat   = 'Cat'

What did you expect to happen?

lines-around-comment rule should take precedence.

What actually happened?

Both rules conflict with each other.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response

[flosker]

@bfelbo No, haven’t added that one. I changed my config (and padded-block rule), that seemed to satisfy my needs.

[bfelbo]

@flosker did you create a rule to include comment as an additional STATEMENT_TYPE?

If so, would be awesome if you could share 😄