Inspired by the book 'Building Evolutionary Architectures' I built tff to help data transformation projects evolve in a desired direction. It comes with a github bot that you can plugin to your CI pipeline.
It aims to let transformation projects evolve in the desired direction by: * ensuring layer boundary integrity; * detect duplicate CTE logic; * catch violations locally and in CI
Core concepts: rules apply to models; checks apply to architecture and DAG checks.
Curious to read what you think. What can be improved? What's missing?
Now I have to decide which of the ERR lints we want to fix and which to exclude :)
I was impressed that it 'just worked' on my dbt project
We're currently using sqlfluff linting but it was a bit finicky to get the pieces configured.
sqlfluff does have linting inside VS Code too though, when it works (python path issues...)