Barry Pollard

And the `StartsClause` and `EndClause` should allow multiple values to handle this case: ``` BEGIN IF .... END IF END ```

Why wouldn’t you want same thing for brackets? I presumed the reason for the negative look aheads in brackets is to prevent matching an opening bracket without a closing bracket...

I don’t think you’ll be able to get away with just defining the Grammar with an opening bracket and a closing bracket at either end if that’s what you mean?...

> More generally, I would expect the same errors to be printed regardless of whether I run fix or lint. Curious, what's your expectation for rules that can't be autofixed?...

> I would at least expect the printing to be consistent – and for the rules it is, right? The example in the issue description demonstrates how the L010 violation...

Does Rule L022 not take care of the second example?

Isn’t this a duplicate of #3512 ?

Happy to keep this open if you can rename the other one. And ideally reduce the huge test case to a minimally viable one that just produces that other error.

Unfortunately there is not much we can do without the SQL that produces this error (ideally a minimal reproducible example SQL) so will need to close this issue if we...

Looks like this simpler example also produces it: ```sql WITH cte1 AS ( SELECT a FROM (SELECT a) ) SELECT a FROM cte1 ``` This only has one linting failure:...