-
Notifications
You must be signed in to change notification settings - Fork 983
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify that tests is backwards compatible to data_tests #5859
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Thank you @joellabes! I totally agree. I think we should also:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One tiny suggestion.
@@ -306,6 +304,8 @@ data_tests: | |||
|
|||
</File> | |||
|
|||
To suppress warnings about the rename, add `TestsConfigDeprecation` to the `silence` block of the `warn_error_options` flag in `dbt_project.yml`, [as described in the Warnings documentation](https://docs.getdbt.com/reference/global-configs/warnings). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can change this warning name once this issue is addressed dbt-labs/dbt-core#10504
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked here, and the TestConfigDeprecation name itself won't change, just the warning message it returns. (Because changing that name would itself be a breaking change!)
Co-authored-by: Leona B. Campbell <[email protected]>
What are you changing in this pull request and why?
In this Slack thread, someone pointed out to me that we're indicating that backwards compatibility for
tests
could be removed at some point in the future.We have no plans to do so, and even if we did decide to do it one day it would go through the behaviour change process, so we don't need to be warning about urgent action or disruption.
Checklist