New bug，ArgumentOutOfRangeException

Hello,

I'm sorry but I'm not seeing this happen when I paste the code snippet into our Visual Basic Editor demo and press the format document button.  Can you verify that you can reproduce this using that demo, and tell us exactly which version/build you are using?

The version I use is 22.1.2, which is a preview version.
There is no problem with the new example, but this problem does exist in my project, but it doesn't matter. I'll use the try statement to solve it. Please check the code of "actiprosoftware. Internal. K7". This method does not judge the legitimacy of position and length when using "substring".

Now I submit a new bug，copy the following code into "syntaxeditor", and then and press the format document button:

Dim lklb As String = "123"
Dim FCURe As String = "ncd"
Select Case lklb
    Case "11", "22"
        If True Then
            If True Then

                Select Case FCURe
                    Case "a", "b", "c"
                        Dim s As String
                    Case Else
                        Dim xmsa() As String = {"1", "2", "3" }
                        For i As Integer = 0 To xmsa.Length - 1
                            If 1 = 1 Then
                            Dim i As Integer = 100
            End If
            Next

End Select
End If

End If
End Select

You will find that the code has not changed. Normally, the code should be:

Dim lklb As String = "123"
Dim FCURe As String = "ncd"
Select Case lklb
    Case "11", "22"
        If True Then
            If True Then
                Select Case FCURe
                    Case "a", "b", "c"
                        Dim s As String
                    Case Else
                        Dim xmsa() As String = {"1", "2", "3" }
                        For i As Integer = 0 To xmsa.Length - 1
                            If 1 = 1 Then
                                Dim i As Integer = 100
                            End If
                        Next
                End Select
            End If
        End If
End Select

Hello,

We would need to be able to debug the issue locally for the substring issue to be able to isolate what could cause that.  If you can tell us how to reproduce it in one of our samples, that would be helpful.

We found the cause of the indenting problem.  It was due to how the parser was assigning an offset range to a switch label AST node when there was a "Case Else" scenario.  It should now be fixed for the next maintenance release.