TypeScript files often produce a false positive about "already declared in the upper scope"

[kaiyoma]

TypeScript files often produce a false positive about "already declared in the upper scope"

[ed-graham]

We are also finding quite a lot of these. Some can be explained, though; for example:

const book= store.books.find(
      book => book.id === session.bookId
    );

Here the fix is quite simple - replace the inner book variable with something else:

const book= store.books.find(
      b => b.id === session.bookId
    );

[vilchik-elena]

Hey,

Since SonarTS 2.0 typescript code is analyzed by SonarJS (SonarTS is basically empty plugin). To avoid any confusion, it's easier to report your problems in https://community.sonarsource.com/, where our team is monitoring the new threads.

About your problem, it's a ESLint rule no-shadow which is run under the hood. Probably it does not work properly for TypeScript files.

I didn't manage to reproduce your mysterious FP @kaiyoma

@ed-graham I believe your case is valid, nothing to improve here.