When working in vscode on a file with a node with a large number of -> inline options (e.g., more than 13), attempting to invoke the custom command completion anywhere after the branch hangs with "Loading...". The more options, the longer the hang (and recovery time of the LSP).
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
Create a node with 13+ -> options and lines of dialogue below each.
Attempt to invoke custom command completion via typing e.g., <<p and pressing ctrl+space after the 13th line of dialogue (indented) or even try to create a whole new node and use it. The call will either never finish or take forever and return no results after many seconds.
Inserting a new node between Bug1 and Bug2 and attempting to use code completion in there works just fine;
What is the expected behavior?
Would expect the typeahead to suggest <<wait>> or <<if>> or <<stop>> etc.
Please tell us about your environment:
Yarn Spinner Version: 2.2.2
Unity Version: 2021.3.12f1
Other information
Here's a copy of my assets folder with the bug (title: Bug2):
Assets.zip
What is the current behavior?
When working in vscode on a file with a node with a large number of
->
inline options (e.g., more than 13), attempting to invoke the custom command completion anywhere after the branch hangs with "Loading...". The more options, the longer the hang (and recovery time of the LSP).Please provide the steps to reproduce, and if possible a minimal demo of the problem:
Create a node with 13+ -> options and lines of dialogue below each.
Attempt to invoke custom command completion via typing e.g.,
<<p
and pressing ctrl+space after the 13th line of dialogue (indented) or even try to create a whole new node and use it. The call will either never finish or take forever and return no results after many seconds.Inserting a new node between Bug1 and Bug2 and attempting to use code completion in there works just fine;
What is the expected behavior?
Would expect the typeahead to suggest
<<wait>>
or<<if>>
or<<stop>>
etc.Please tell us about your environment:
Other information
Here's a copy of my assets folder with the bug (title: Bug2): Assets.zip