Open joerg-holtmann opened 2 years ago
Not really, actually, when you input some whitespace after shortName identifier in the rule AnalysisFunctionType, you will still be proposed with opening curly brace, it's in the relatively behind in the queue. @joerg-holtmann
For many elements like
FunctionFlowPort
, the auto-completion proposes a opening curly brace after theshortName
identifier independent of how many whitespaces follow theshortName
identifier. This is the expected editor behavior.However, for some elements like
AnalysisFunctionType
, the opening curly brace is only proposed directly following theshortName
identifier. If one puts any whitespace after theshortName
identifier, the opening curly brace doesn't get proposed.This is due to the following differences in the grammar:
FunctionFlowPort
and similar elements have a style likeshortName=Identifier '{' ... '}';
AnalysisFunctionType
and similar elements have a style likeshortName=Identifier ('{' ... '}')?;
Can we fix this and handle uniformly, ideally like the first style to allow arbitrarily many whitespaces preceding the opening curly brace?