David Seddon

Nice idea! I'd be happy to consider a pull request. You might want to start by creating [a custom contract type](https://import-linter.readthedocs.io/en/stable/custom_contract_types.html) that you can use on your project. It shouldn't...

Great idea! This isn't a priority for me at the moment but I'd welcome a contribution on this. If anyone is interested in exploring contributing this, please reach out and...

Hi Nathan, Great to hear it. Can I suggest we begin by defining an acceptance test, e.g. the API you would expect to be able to call and the a...

@dedsm Could you go into a bit more detail about how this might look like for you?

Thanks, that's helpful. I'm thinking a system that supports pluggable formats would be a good idea - would also address https://github.com/seddonym/import-linter/pull/288.

Another approach to making this a CLI argument would be to provide a Python API for running Import Linter (something I've been meaning to do anyway) with a structured return...

But you're extension is going to have to run some Python somehow, right? So perhaps a good approach would be to for you to write the wrapper Python CLI in...

> maybe add the time of the contract run I don't think this is necessary, unless you have a use case in mind? > i dont know exactly where to...

Related PR: https://github.com/seddonym/import-linter/pull/293 - which outputs everything in a json format. We should consider both of these use cases, I'm still considering what the best design is but feel free...

Thanks for your suggestion! (I also didn't know that Tach was no longer being maintained.) I am on the fence on this one. A fundamental principle of Import Linter is...