ESLint fixes are no longer available after enabling the examples processor

[lishaduck]

Expected behavior

ESLint should continue to provide fixes for .ts files.

Actual behavior

ESLint no longer provides any fixes for any rules in files that the processor runs on.

ESLint Config

{
  name: "deputy/docs/examples/setup",

  plugins: {
    examples: getJsdocProcessorPlugin({
      checkDefaults: true,
      checkParams: true,
      checkProperties: true,

      exampleCodeRegex: "^```([\\s\\S]*)```\\s*$",

      parser: ts.parser as Linter.Parser,
    }),
  },
  processor: "examples/examples",
},

ESLint sample

I've been testing with unicorn-x/no-negated-condition

!boolean ? some : val

Environment

• Node version: v24.2.0
• ESLint version v9.31.0
• eslint-plugin-jsdoc version: 51.3.1

[brettz9]

There were unfortunately more problematic side effects when we had enabled supportsAutofix on the processor, and it appears that setting it to false disables all fixes, as you have discovered, rather than just the fixes of the processor. The ideal solution would of course be to get fixing working for the processor, but getting things to work with whitespace and such was rather complicated, and I'm not inclined to work on this myself. I think we need to simply document that this is an unfortunate side effect of using the processor.