enforce layers split

[gforcada]

We are moving a few addons to be core-addons, plone.api should not be used in a few places, but fine in others...

That's all great but in practicality impossible to double check manually on a PR basis unless you have a tool... 🥁 enters import-linter:

https://import-linter.readthedocs.io/en/stable/index.html

Although the main use case is to check dependencies between packages of a single python distribution, it says on the docs that it can handle external packages as well ✨🍀

That sounds like the perfect fit to our organization layer cleanup, right?

@jensens @mauritsvanrees

[jensens]

Wow, this sounds like a great tool. -> Wanna have!
This could be expanded in future for other checks as well.

[mauritsvanrees]

Cool!

[mauritsvanrees]

The Python Weekly Newsletter has an article on organising a large code base with layers, and it also mentions import-linter:
https://blog.europython.eu/kraken-technologies-how-we-organize-our-very-large-pythonmonolith/

[gforcada]

Yes, I took it from there 😄