Fields that come from macros should come from macros always #27
Labels
category:models
Related to the models in the package.
priority:low
Not on the roadmap.
status:completed
Completed - but might not be released yet.
type:enhancement
New features or improvements to existing features.
Is your feature request related to a problem? Please describe.
Sometimes we refer to columns that have come from field group macros by macro, and sometimes by name. We should use the macro throughout to make it easier to make changes in the future, and in case a user overwrites the macro.
e.g.
dbt-snowplow-unified/models/sessions/scratch/snowplow_unified_sessions_this_run.sql
Lines 35 to 37 in ba00cac
dbt-snowplow-unified/models/sessions/scratch/snowplow_unified_sessions_this_run.sql
Lines 383 to 388 in ba00cac
Describe the solution you'd like
Describe alternatives you've considered
Additional context
Are you interested in contributing towards this feature?
The text was updated successfully, but these errors were encountered: