After some discussion with product and dev experience, we've decided to change the name of this field. It hasn't shipped to core yet so is not a breaking change. The name change is intended to remove the word "default", which should be implied for a YAML field. This is more consistent with other dbt YAML objects, which have a default in YAML that can be overridden at query time. The name time_granularity is also more consistent with the field we have on time dimensions.
Everything in this PR is just a find & replace operation.
Description
After some discussion with product and dev experience, we've decided to change the name of this field. It hasn't shipped to core yet so is not a breaking change. The name change is intended to remove the word "default", which should be implied for a YAML field. This is more consistent with other dbt YAML objects, which have a default in YAML that can be overridden at query time. The name
time_granularityis also more consistent with the field we have on time dimensions. Everything in this PR is just a find & replace operation.Checklist
changie newto create a changelog entry