alpharush

Right now, crytic-compile isn't taking into account imports when it creates that standard json input, but this is definitely something we want to improve (for solidity as well). Ideally, we'd...

My mistake. The ability to standalone compile with a glob target the recurses into subfolders isn't yet implemented. It caused issues with projects that mix Solidity and Vyper as it...

For reference here is the issue on getting ape to support what other compilation frameworks provide https://github.com/ApeWorX/ape/issues/1590

I experimented with [ automatically resolving](https://github.com/crytic/crytic-compile/pull/508) the imports but crytic-compile/ slither both expect absolute paths while Vyper seems to expect the standard json to have something like `interfaces/IAccessControl` in the...

This would have to detect that the current select version is not compatible with the pragma in order to be useful. Otherwise it would override the solc version even if...

Are you using a compilation framework like hardhat or foundry? That's necessary to resolve the imports

Does `hardhat compile` work? Looking at this again I noticed these are compilation issues from solc, not crytic-compile. It also appears that you may be on an old version of...

We would need to create a new compilation unit every time a file compiles with a given version. Also, we could consider just parsing the pragma and switching the solc...

@MarHalborn Would you upgrade to the latest slither version as the latest release fixed many issues related to aliased imports? Let us know if it is still not working please

This lines need to be update to include internal state variables: https://github.com/crytic/slither/blob/0ec487460690482c72cacdea6705e2c51bb3981e/slither/detectors/naming_convention/naming_convention.py#L165