feat: only report ESLint errors for unresolvable relative Imports #237

[wolfmanfx]

Change ESLint adapters to report “cannot be resolved” only for relative imports (starting with .), while continuing to track all unresolvable imports internally for data/export.

Why

• Reverts behavior introduced in 12b5c1e that caused false positives for external libs and Node built-ins.

Notes

• No dependency changes; zero-dependencies policy upheld.
• Docs not impacted beyond behavior clarification.

Breaking changes

• None for consumers relying on CLI export/data.
• ESLint surfaces fewer unresolvable import errors (only relative ones).

Checklist

• Unit tests pass: yarn test
• Lint: yarn lint:all
• Build: yarn build:all
• Integration tests: ./run-integration-tests.sh - There is an issues

Summary:

• Implemented selective ESLint reporting using isRelativeImport.
• Preserved internal tracking in UnassignedFileInfo/FileInfo.
• Updated and added tests to reflect the new behavior.

[rainerhahnekamp]

Super Murat, just very tiny details. Can you maybe add in the main.ts for angular-iv and angular-i an import to keycloak. With your change you don't to modify anything else and the integration tests should not report that as unresolvable import.

[rainerhahnekamp]

Sorry, my fault. The integration tests have actually been upgraded and are now failing because of the new behavior. Murat, do you want to try it and fix them or should I just merge and push the integration test fixes in a separate PR?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wolfmanfx]

@rainerhahnekamp I have removed the assertion for import 'logo.jpg'; as this not a local import we ignore it