Import Linter's config file format is not expressive enough for all use cases. For example, users might want to configure contracts based on the contents of the filesystem, rather than listing items explicitly.
A powerful feature would be to make it possible to run Import Linter in a more dynamic way. One way to achieve this would be to provide a Python API that allows passing in of contracts and configuration at runtime, rather than by reading from a file. That would allow users to write wrapper scripts.
Another approach would be to provide a hook mechanism for people to generate the contracts, but still use the lint-imports CLI entry point.
Another: allow passing in config via stdin.
Import Linter's config file format is not expressive enough for all use cases. For example, users might want to configure contracts based on the contents of the filesystem, rather than listing items explicitly.
A powerful feature would be to make it possible to run Import Linter in a more dynamic way. One way to achieve this would be to provide a Python API that allows passing in of contracts and configuration at runtime, rather than by reading from a file. That would allow users to write wrapper scripts.
Another approach would be to provide a hook mechanism for people to generate the contracts, but still use the
lint-importsCLI entry point.Another: allow passing in config via stdin.