On #17 we found that the no-unused-imports rule tries to read the imported path relative the the directory where the solium command is being executed, not relative to the file currently being analyzed.
That means that if we run solium on a directory root, and there is a file in root/contracts/TestImport.sol with a statement like import './TestImported.sol', we will try to find this file in root/TestImported.sol instead of root/contracts/TestImported.sol.
To fix this, we need a change in solium because the rule currently has no access to the path of the file being analyzed.
On #17 we found that the no-unused-imports rule tries to read the imported path relative the the directory where the solium command is being executed, not relative to the file currently being analyzed.
That means that if we run solium on a directory
root, and there is a file inroot/contracts/TestImport.solwith a statement likeimport './TestImported.sol', we will try to find this file inroot/TestImported.solinstead ofroot/contracts/TestImported.sol.To fix this, we need a change in solium because the rule currently has no access to the path of the file being analyzed.