[CT-1201] [Bug] Metrics don't require expression
field
#5871
Labels
bug
Something isn't working
help_wanted
Trickier changes, with a clear starting point, good for previous/experienced contributors
semantic
Issues related to the semantic layer
Milestone
Is this a new bug in dbt-core?
Current Behavior
Ran into this behavior when working with a beta customer. Right now, we provide the default value of empty string ("") to the expression/sql field. That then gets provided to ParsedMetric where it recognizes this field as a string and accepts it, even if the field isn't defined in the metric.
Expected Behavior
If the expression field isn't present, the metric would fail to compile.
Steps To Reproduce
The text was updated successfully, but these errors were encountered: