David Seddon

Another option: we start accepting the config files as positional arguments to `lint-imports`. That would allow us to leverage the user's shell for glob expansion (in the same way as...

# How to handle top-level configuration The main design consideration with supplying more than one file is that there might be more than one [top level configuration](https://import-linter.readthedocs.io/en/stable/usage.html#top-level-configuration). I think we...

# How to handle contracts with identical ids The linter can currently be run on specific contracts by passing `--contract`. https://import-linter.readthedocs.io/en/stable/usage.html#running-the-linter. This uses the `id`, which will always be present...

On the above comments, my current thinking is that we should maximise flexibility - so someone should be able to combine runs across multiple files without needing to edit the...

I love this! I have actually been thinking about expanding the scope of Import Linter beyond just a linter, for more visualization tooling. In particular I have been wondering if...

Thanks for the issue. > Is the above expected to work? If so, how? It should work if you're running pre-commit from within your virtual environment - it says that...

Hmm, to be honest I'm not sure there is an ideal way to configure pre-commit. Import Linter is designed to work with with access to any analyzed packages on the...

Hi Remi - apologies for the breaking change - it seems it's a bit awkward to get the installable precommit to work out of the box in all environments. I...

Great, glad you got it working.