You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Functionality to apply automatic fixes where possible in the style of sqlfluff fix or rubocop --autocorrect.
For example, Hard Coded References violations could be automatically resolved by querying the DAG for a relevant reference and replacing the hardcoded table name.
Depending on the nature of the violations, this could expedite the process of having an existing dbt project conform to best practices. I'd like to implement a CI check but our project currently has 461 outstanding violations after running the evaluator for the first time, many of which I suspect are automatically fixable. If I could automatically resolve 50% of those, it would allow me to focus on more substantive project changes and get closer to implementing a CI check.
Are you interested in contributing this feature?
No
The text was updated successfully, but these errors were encountered:
Describe the feature
Functionality to apply automatic fixes where possible in the style of
sqlfluff fix
orrubocop --autocorrect
.For example, Hard Coded References violations could be automatically resolved by querying the DAG for a relevant reference and replacing the hardcoded table name.
Describe alternatives you've considered
Implementing recommendations by hand.
Additional context
Who will this benefit?
Depending on the nature of the violations, this could expedite the process of having an existing dbt project conform to best practices. I'd like to implement a CI check but our project currently has 461 outstanding violations after running the evaluator for the first time, many of which I suspect are automatically fixable. If I could automatically resolve 50% of those, it would allow me to focus on more substantive project changes and get closer to implementing a CI check.
Are you interested in contributing this feature?
No
The text was updated successfully, but these errors were encountered: