Ted Conbeer

Also dbt-power-user added support. Closing this, as the other options are all documented at docs.sqlfmt.com

I was all caught up on the collision with other valid sql syntax, like this statement that should select two strings in columns foo and bar: ```sql select '{{ my_macro('...

Yep! Have to be careful with other types of statements (create function/table) also

Thanks. Still looking for help researching the various uses for the colon in different dialects

Related: consider formatting code in `set` blocks, if we can clearly detect that it's sql (e.g., if it starts with `select ...`). This is maybe a bad idea, but inspired...

From pg-promise [docs](https://github.com/vitaly-t/pg-promise?tab=readme-ov-file#named-parameters): ## Named Parameters When a query method is parameterized with values as an object, the formatting engine expects the query to use the Named Parameter syntax `$*propName*`,...

`glob.glob` and `Path.glob` both match paths, whether you use forward or single or doubled backslashes. So there must be an issue either with the way that Click passes in these...

My guess is we're parsing this as a triple-quoted expression followed by a single quote. We get this right (postgres dollar sign quotes): ``` select $$'$$ || 'quoted_text' || $$'$$...

thanks for the report. Snowflake has similar syntax for like, ilike, etc., as functions instead of infix operators. While this formatting isn't ideal, snowflake parses it and accepts it as...

I'm not going to tackle this right now -- because of how the lexer and parser work, it's non-trivial to distinguish between `rlike('foo, bar')` and `rlike('foo', 'bar')` when these tokens...