Improving message description for compile error in get_fixtu…

dbt-labs / dbt-adapters

Apache License 2.0

25 stars 35 forks source link

Improving message description for compile error in get_fixtu… #203

Closed AlejandroBlanco2001 closed 4 months ago

AlejandroBlanco2001 commented 4 months ago

resolves https://github.com/dbt-labs/dbt-core/issues/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

[X] I have read the contributing guide and understand what's expected of me
[X] I have run this code in development, and it appears to resolve the stated issue
[X] This PR includes tests, or tests are not required/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX

cla-bot[bot] commented 4 months ago

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

github-actions[bot] commented 4 months ago

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.

AlejandroBlanco2001 commented 4 months ago

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