Cameron
Cameron
This has been fixed in #4996
Thanks for the report! This appears to have been fixed by #5728.
This appears to be caused by the combination of LT02 and ST09 being applied to the same slice location. The fix skips over the overlapping slices dropping some of the...
@jmc-bbk You can run any of the sqlfluff commands with `-vvvv` to get the debug level of logging. My typical workflow: ```sh mkdir test_sql/sqlfluff_5641 # add example query to this...
This specific example now works in 3.0.0a6 pre-release and should be fixed in the 3.0.0 release.
@david-shanks Can you provide an example query where this produces the failure to parse?
This might be a duplicate of #5484 which is fixed in main and will be in the next release.
> **2 - Run the BQ dialect test by running : python test/generate_parse_fixture_yml.py -d bigquery** > > * I get this output always : > _"Match Pattern Received: > filter=*...
It looks like you are using the dbt templater here. Have you enabled the `executeInTerminal` option in the settings? ```json "sqlfluff.experimental.format.executeInTerminal": true, ``` Take note of the `formatOnSave` warning: >...
Ideally yes, however, the current implementation of this extension's default mode is to take the output from stdout and replace the content with that output. When using the dbt templater,...