Fix constructor highlighting when opening parenthesis on new line #350
+60
−32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Syntax highlighting breaks for all code following a constructor when the opening parenthesis is placed on a new line:
Root cause: The
constructor-declarationpattern used a lookahead(?=identifier\s*\()that only matched when both the constructor name and(were on the same line. When split across lines,property-declarationmatched instead, consuming the identifier and breaking subsequent parsing.Changes:
class-or-struct-memberspatterns to checkconstructor-declarationbeforeproperty-declarationandfield-declaration(?=@?[_[:alpha:]][_[:alnum:]]*\s*\()to(@?[_[:alpha:]][_[:alnum:]]*)\s*(?=\(|$)to match identifiers at end-of-linematchtobeginCapturesfor cleaner pattern structureThe pattern now matches when the identifier is followed by
(on the same line OR at end-of-line, with the actual(matched by the subsequentparenthesized-parameter-listinclude.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.