Jeremy Cohen

I found a simple fix for this, but I'd be curious to get @nathaniel-may's take on it before merging

@bilalaslamseattle Thanks for flagging this again. We've seen multiple issues in this category, across multiple adapters, and we think there exists a general-purpose solution that will be the right move...

@tiffanygwilson Very cool issue, thanks for opening! I think the specific use case you're outlining, which I'll call **"UDF management,"** deserves to be considered and tackled as its own problem—a...

We're thinking more about UDF management, and it's increasingly likely we treat these as a first-class resource type in a future release: https://github.com/dbt-labs/dbt-core/discussions/5741 > We may not want to update...

Prior attempt: https://github.com/dbt-labs/dbt-core/pull/3498 And discussion about exactly which file extension to add support for: https://github.com/dbt-labs/dbt-core/issues/3484 We ran into some thorny errors in unit tests that were more difficult to debug...

It's been a while since that PR, but it was trickier business than we anticipated. If I recall correctly, I _think_ one of the tricks was around `.sql.jinja` containing a...

Got it - yeah it looks like the default file associations for that VSCode extension are the ones recommended by the Jinja maintainers, namely another `.extension` signifying Jinja: > **Jinja...

In order to reproduce this: - Custom generic test definition that references a `dbt.*` macro that was moved from `dbt_utils` - A version of the `dbt_utils` package installed with backwards...

Taking another look here, since we might want to consider recommending `dbt.*` as the go-forward standard, instead of calling utility macros out of the global namespace, and this bug is...

I'm going to un-stale this, I'd still like to do it someday :)