Lee Powell

Should this be considered a feature request as per ‘label-has-associated-control’, - or would it be to difficult to work out the reverse relationship via id/htmlFor. Currently we're having to disable...

👍

@lifeiscontent - try using: https://www.npmjs.com/package/eslint-import-resolver-typescript

@ljharb - would there be any appetite for `import/extensions` rule to support a typescript option which would allow `.ts` and `.tsx` to be equivalent to a `.js` extension which the...

@ljharb - sorry, do you mind explaining what the Typescript bug/flaw is? Currently I'm struggling to be able to enforce `.js` extensions in a project using Typescript using this rule...

@ljharb Typescript doesn't explicitly force you to omit extensions. It won't let you use `.ts` ot `.tsx` as an extension, but `.js` is perfectly valid (https://github.com/microsoft/TypeScript/issues/16577). This allows me to...

Looking at the src for `extensions` rule I believe this plugin would still error even if anything was done in the resolver. I have to disagree that supporting this feature...

I'm not sure about that ... I think it resolves just fine (would need to check), but then simply check that the file extensions match. Obviously it fails as expected...

Sure, and I don't think this has to be typescript specific if we can expose a config option to support alternative relationships between extensions. ``` "import/extensions": [ , "never" |...

@patrickarlt so if we just **don't** use `eslint-import-resolver-typescript` then this works?