Visual Basic is case-insensitive, but the onEnterRules patterns in language-configuration.json were matching keywords case-sensitively. This meant indentation behavior would fail for code written as "end if" or "END IF" instead of "End If".

Changes

• Converted all onEnterRules patterns from string format to object format with "flags": "i"
  • beforeText pattern in first rule (End statements and block terminators)
  • previousLineText pattern in second rule (blank line after block terminators)
  • beforeText pattern in third rule (lines ending with closing parenthesis)

// Before
"beforeText": "^\\s*((End\\s+If)|Else)\\b.*$"

// After
"beforeText": { "pattern": "^\\s*((End\\s+If)|Else)\\b.*$", "flags": "i" }

This aligns with patterns used in HTML and Handlebars language configurations for case-insensitive languages.

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.