[Fix] Fixing typo in IDE section

[darkartur]

Fixes #1743

[coveralls]

Coverage remained the same at 97.787% when pulling a1c969f on darkartur:master into 40ee069 on benmosher:master.

[coveralls]

Coverage remained the same at 97.739% when pulling 3e06a10 on darkartur:master into 92caa35 on benmosher:master.

[coveralls]

Coverage remained the same at 97.739% when pulling 3e06a10 on darkartur:master into 92caa35 on benmosher:master.

[coveralls]

Coverage remained the same at 97.739% when pulling 3e06a10 on darkartur:master into 92caa35 on benmosher:master.

[ljharb]

Can you provide a test case, that would have prevented this from happening?

[darkartur]

Can you provide a test case, that would have prevented this from happening?

I wanted, but I haven't found any similar cases in tests. It requires a big work to achieve this.

If I understand right test cases covers rules but don't covers IDE integrations.

I test this by running two files in row:

// Component/index.ts
export { default } from './Component.tsx';

// Component/Component.tsx
export default function Component() {
}

It fails when I run like this:

eslint ./Component/index.ts ./Component/Component.tsx 

But pass if run in opposite direction:

eslint ./Component/Component.tsx ./Component/index.ts

I don't sure that I can reproduce this behaviour in tests

[ljharb]

Maybe I'm a bit confused; #1743 doesn't have much background. It shouldn't be possible for an IDE integration to do anything different than is done on the command line; if something works on the CLI but breaks in an IDE, the IDE itself is broken, full stop.

[darkartur]

Maybe I'm a bit confused; #1743 doesn't have much background. It shouldn't be possible for an IDE integration to do anything different than is done on the command line; if something works on the CLI but breaks in an IDE, the IDE itself is broken, full stop.

Please take a look to update of my previous message

[ljharb]

Interesting, thanks - I'd bet you could add that setup inside https://github.com/benmosher/eslint-plugin-import/tree/master/tests/files, and that might lead to reproducing it?

[darkartur]

Interesting, thanks - I'd bet you could add that setup inside https://github.com/benmosher/eslint-plugin-import/tree/master/tests/files, and that might lead to reproducing it?

I can try, but how I can run two files in row in test?

[darkartur]

Interesting, thanks - I'd bet you could add that setup inside https://github.com/benmosher/eslint-plugin-import/tree/master/tests/files, and that might lead to reproducing it?

It was easier then I thought. My example was wrong a bit. This is right example:

// Component/components.ts
export { default as Component } from './Component.tsx'; // this used somewhere else

// Component/Component.tsx
export default function Component() {
}

eslint ./Component/components.ts ./Component/Component.tsx // fails
eslint ./Component/Component.tsx ./Component/components.ts // pass

[darkartur]

I have found another case and fixed it too but I think this function have even more issues.

[darkartur]

@ljharb what else can I do to merge this?