Better error messaging for malformed source/ref inputs #1660
Labels
enhancement
New feature or request
good_first_issue
Straightforward + self-contained changes, good for new contributors!
Milestone
Feature
Catch malformed inputs to
source()
andref()
functions and elegantly bubble up to end user.Current error messaging is non-obvious
had a colleague who is new to dbt encounter the following cryptic error today:
my hunch, knowing a good amount about dbt, was that this was related to a malformed
source()
call, was correct, as he only passed one arg into that fn instead of two:even with the
--debug
flag, this was difficult to track downRequest
It seems like these sorts of errors could be caught and communicated more effectively (I can't imagine my colleague is the first or last one to make this mistake), to output something like:
Who will this benefit?
This will benefit any user who mistakenly leaves out a schema designation in her
source()
usage, or mistakenly includes a schema designation in aref()
call.The text was updated successfully, but these errors were encountered: