David Seddon

I think the simplest approach would be to allow wildcards in `DirectImport`s (which already is the case) add an optional `explode_wildcards` argument to the `pop_imports` helper. The contracts implementing `ignore_imports`...

> My worry about moving the "explosion" to pop_imports is, that the methods in Module like parent or is_child_of need to be able to handle wildcards as well. Hmm, you...

Thanks for this. For me, it sounds like the big win is that it might help others contribute to the project. I'd be happy to consider a PR if you...

What a good idea - yes I agree, this would make sense. My follow up question would be, is there anyone that would actually use that feature right now? Knowing...

Thanks for the feature request. I think this is a good idea. I've renamed the issue accordingly. If you're eager to see a feature like this soon, you *could* implement...

> I will try to prepare initial implementation in following weeks Thanks @skarzi. You should be able to do this without any changes to core import-linter by implementing a custom...

Thanks for the suggestion and sorry for the delay, I've been on holiday. It's an interesting idea. Is something like this what you are envisaging? ``` [importlinter:contract:1] name = Restrict...

I agree, I think the Protected contract would be the best way forward. Happy to consider a PR at some point - in the meantime you can always make a...

Hi Iwan, Thanks for your message - great idea! If you'd find this useful, you may be interested that you can create custom contract types - so you don't need...

I'm going to close this in favour of these issues: - https://github.com/seddonym/import-linter/issues/159 - https://github.com/seddonym/import-linter/issues/158