eslint-plugin-eslint-plugin
eslint-plugin-eslint-plugin copied to clipboard
eslint-community
Rule: report locations should be based on ESTree node ranges
From https://github.com/typescript-eslint/typescript-eslint/issues/4796:
Following https://github.com/typescript-eslint/typescript-eslint/issues/4723 and https://github.com/typescript-eslint/typescript-eslint/pull/4790, it looks like we need to might need to always report fixer ranges using the ES tree nodes rather than TypeScript nodes. If that's the case (is it?) we should lint to make sure we don't accidentally use a TypeScript node.
How about the rule use type information to check that if an object's property is provided as an argument to a fixer's range parameter, it should come from an ESTree node's .range
This partially reopens #6.
