Closed WebStew closed 6 years ago
Hi,
In my TypeScript project I am using path aliases to my files as per the below from my tsconfig.json
{ ... "paths" : { "@features/*" : "project/features/*" } ... }
SonarQube is reporting the following Code Smell for each time I call an import using the alias
Module @features/ is not listed as dependency in package.json.
Is this the correct behaviour? I wouldn't expect a Code Smell here but rather for SonarQubeTS to be aware of my path aliases?
Many thanks Stu
Closing issue as logged https://github.com/SonarSource/SonarTS/issues/677 here
Hi,
In my TypeScript project I am using path aliases to my files as per the below from my tsconfig.json
{ ... "paths" : { "@features/*" : "project/features/*" } ... }
SonarQube is reporting the following Code Smell for each time I call an import using the alias
Module @features/ is not listed as dependency in package.json.
Is this the correct behaviour? I wouldn't expect a Code Smell here but rather for SonarQubeTS to be aware of my path aliases?
Many thanks Stu