layer_linter
layer_linter copied to clipboard
seddonym
This package is deprecated - use Import Linter instead.
Currently when we do a release, the test run actually fails: https://travis-ci.org/seddonym/layer_linter/builds/450960486 This is because the conditional deploy in the `.travis.yml` requires Python 3.6, which multiple items in the Travis...
Eg, I'd like the ability to say that modules in `utils` may not import from from any path that matches `apps.*.models`.
"A closed layered architecture means that any given layer (or tier) can only use the services of the next immediate layer, whereas in an open layer architecture a given layer...
``` My contract: containers: - mypackage.apps.* layers: - views - models ``` In this case, any apps within `mypackage.apps` would be linted to check that their models don't import from...
* Layer Linter version: latest * Python version: 3.6 * Operating System: macOS ### Description Layer linter takes a while to run on a moderately sized codebase. This is understandable...
If there is a syntax error in a container module, the linter will crash. Better to handle the SyntaxError gracefully.
It is not very obvious if someone includes a layer that is invalid or nonexistent. This is a particular problem when getting started (e.g. misunderstanding the format of `layers.yml`), but...
Layer Linter currently doesn't import modules that contain the word 'migrations', in order to avoid importing Django migrations. It would be better if this could be configurable on a project-by-project...
This shouldn't be a success: ``` ============ Layer Linter ============ --------- Contracts --------- Analyzed 0 files, 0 dependencies. --------------------------------- Architecture KEPT Contracts: 1 kept, 0 broken. ```