We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using the documentation editor to create tests, tests are expected to be created with the "data_tests" property.
When using the documentation editor to create tests, tests are being created with the "tests" property, which is deprecated.
Open the documentation editor, add data tests, inspect created yml.
No response
Windows 11
dbt Cloud CLI - 0.38.15 (Versionless)
Fabric
v0.46.0
The text was updated successfully, but these errors were encountered:
@joshrodgersKA is this happening while creating tests for model or column? Do you mind record a video for us to validate the issue?
Sorry, something went wrong.
@saravmajestic - I'm seeing it happen when creating tests for columns. I've attached a video. Let me know if you need anything else. Thanks!
Thank you @joshrodgersKA Video is really helpful. I have identified the issue and will release a fix soon
@joshrodgersKA this fix is released in v0.47.6. Please re open this if you still see this issue
saravmajestic
Successfully merging a pull request may close this issue.
Expected behavior
When using the documentation editor to create tests, tests are expected to be created with the "data_tests" property.
Actual behavior
When using the documentation editor to create tests, tests are being created with the "tests" property, which is deprecated.
Steps To Reproduce
Open the documentation editor, add data tests, inspect created yml.
Log output/Screenshots
No response
Operating System
Windows 11
dbt version
dbt Cloud CLI - 0.38.15 (Versionless)
dbt Adapter
Fabric
dbt Power User version
v0.46.0
Are you willing to submit PR?
The text was updated successfully, but these errors were encountered: