For many elements like FunctionFlowPort, the auto-completion proposes a opening curly brace after the shortName identifier independent of how many whitespaces follow the shortName identifier. This is the expected editor behavior.
However, for some elements like AnalysisFunctionType, the opening curly brace is only proposed directly following the shortName identifier. If one puts any whitespace after the shortName 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 like shortName=Identifier '{' ... '}';
AnalysisFunctionType and similar elements have a style like shortName=Identifier ('{' ... '}')?;
Can we fix this and handle uniformly, ideally like the first style to allow arbitrarily many whitespaces preceding the opening curly brace?
For many elements like
FunctionFlowPort, the auto-completion proposes a opening curly brace after theshortNameidentifier independent of how many whitespaces follow theshortNameidentifier. This is the expected editor behavior.However, for some elements like
AnalysisFunctionType, the opening curly brace is only proposed directly following theshortNameidentifier. If one puts any whitespace after theshortNameidentifier, the opening curly brace doesn't get proposed.This is due to the following differences in the grammar:
FunctionFlowPortand similar elements have a style likeshortName=Identifier '{' ... '}';AnalysisFunctionTypeand 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?