Allow .sql.jinja file extension.

Describe the feature

Provide the option to allow *.sql.jinja files as alternative to *.sql in all places where DBT uses jinja in SQL (I believe that is all places excluding the target folder).

This allows users to easily configure their IDE to handle both plain sql files as well as dbt sql(.jinja) files as intended. Currently (at least with pycharm) I have to choose between having all sql files interpreted as jinja or as plain sql.

Describe alternatives you’ve considered

I’ve looked into options to only apply jinja interpretation to the dbt/ part of my project via my IDE but that is not possible. Not only that I’d prefer a configuration that would have the IDE interpret files properly by default, or at least irregardless of project-specific configuration. This one simple change would ensure that.

Who will this benefit?

Everybody 😉

Are you interested in contributing this feature?

Sure

[jtcohen6]

Going to reopen this one, given renewed interest

[jtcohen6]

@Luttik You’re totally right. I’m going to start using help_needed in place of good_first_issue when something:

• Is tricky to implement (but possible, we think, with a clear place to start)
• Depends on community initiative/contribution (we aren’t able to prioritize it ourselves)