When using the analyzer in a project I had problems when using symlinked dependencies.
In the project I installed a component library as a symlinked dependecy using lerna.
The no-missing-import rule didn't work as expected in this situation.
The analyzer created a missing-import warning for every custom Element I used from this library (even though the required import statements were present).
When the required import statements were NOT present, the analyzer didn't supply the codefix to add them.
This behaviour occurs because the analyzer cannot follow symlinked dependencies that are out of the scope of the project.
With this PR symlinked dependencies can be followed. When a symlinked module is discovered in dependency traversal, the analyzer now uses the actual path of the symlinked module rather than the path that the symlink resolves to.
When using the analyzer in a project I had problems when using symlinked dependencies. In the project I installed a component library as a symlinked dependecy using lerna.
The no-missing-import rule didn't work as expected in this situation.
This behaviour occurs because the analyzer cannot follow symlinked dependencies that are out of the scope of the project. With this PR symlinked dependencies can be followed. When a symlinked module is discovered in dependency traversal, the analyzer now uses the actual path of the symlinked module rather than the path that the symlink resolves to.
Any feedback is welcome.