eslint(prefer-destructuring) appears to have a safe fix, but it's not suggested in VSCode, like other fixes

[hamirmahal]

eslint(prefer-destructuring)

appears to have a safe fix, but it's not suggested in VSCode, like other fixes.

[hamirmahal]

https://github.com/hamirmahal/oxc-object-literal-no-quick-fix-in-vscode reproduces the issue.

[hamirmahal]

Here's a screen recording of the issue in VSCode.

no-vscode-quick-fix-for-safe-destructure-fix.webm

[hamirmahal]

const obj = {
    firstName: "Aisha",
}

const firstName = obj.firstName;

console.log(firstName);

[hamirmahal]

.oxlintrc.json

{
	"$schema": "https://raw.githubusercontent.com/oxc-project/oxc/main/npm/oxlint/configuration_schema.json",
	"categories": {
		"restriction": "deny",
		"style": "deny",
	},
}

[hamirmahal]

$ npx oxlint --version && npx oxlint .
Version: 1.35.0


  × eslint(no-console): Unexpected console statement.
   ╭─[object.ts:7:1]
 6 │ 
 7 │ console.log(firstName);
   · ───────────
   ╰────
  help: Delete this console statement.

  × eslint(prefer-destructuring): Use Object destructuring.
   ╭─[object.ts:5:19]
 4 │ 
 5 │ const firstName = obj.firstName;
   ·                   ─────────────
 6 │ 
   ╰────
  help: Use object destructuring rather than direct member access.

Found 0 warnings and 2 errors.
Finished in 10ms on 1 file using 8 threads.

[hamirmahal]

I can't upgrade to the latest version of

oxlint

at the time of this writing, v.1.36.0, because of #17510.