-
Notifications
You must be signed in to change notification settings - Fork 36
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
Improving message description for compile error in get_fixtu… #203
Improving message description for compile error in get_fixtu… #203
Conversation
Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA. In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR. CLA has not been signed by users: @AlejandroBlanco2001 |
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
|
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.
looks good!
note: this is simply an update to the language in an exception we're raising, to provide the end user with greater clarity on the error :)
…ror-description-for-model-not-existing
resolves dbt-labs/dbt-core#10014
Problem
When running SQL unit tests, when a relation does not exist (or the model does not exist), a compilation error is thrown which does not give any idea why this is happening.
Solution
Therefore, a small new feature is added where the error message is improved to give a better idea on how to resolve the error when running the test.
Checklist