You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Yarn Spinner VSCode extension reports a problem in my Yarn file, "Unexpected "T" while reading a return statement", when reading the command <<returnToMainMenu>>
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
I created a function in my application "returnToMainMenu".
I defined it in my Functions.ysls.json file.
I added the command to one of my Yarn files.
The Yarn Spinner VSCode extension reports the problem noted above, with the 'T' in ToMainMenu underlined in red.
The only issue is the report in VSCode.
This does not manifest in any problems during execution of the application - the custom function is still parsed and called as expected, and works fine.
What is the expected behavior?
No error message.
Please tell us about your environment:
Yarn Spinner Version: v2.4.21 (pre-release)
Unity Version: N/A
Other information
I'm somewhat at a loss. I don't know VS Extensions well enough to diagnose!
The text was updated successfully, but these errors were encountered:
I think this is actually a bug in our parser! The parser is reading “return”, thinking it’s the return keyword, and getting confused from there. (This doesn’t happen with other keywords like if, because those are actually defined to include a space afterwards to prevent this issue.)
Yup, I figured it would be something like that. That makes sense to me! Thanks, Jon. It's not that annoying, and I'll just name the function "backToMainMenu".
What is the current behavior?
The Yarn Spinner VSCode extension reports a problem in my Yarn file, "Unexpected "T" while reading a return statement", when reading the command
<<returnToMainMenu>>
Please provide the steps to reproduce, and if possible a minimal demo of the problem:
The only issue is the report in VSCode.
This does not manifest in any problems during execution of the application - the custom function is still parsed and called as expected, and works fine.
What is the expected behavior?
No error message.
Please tell us about your environment:
Other information
I'm somewhat at a loss. I don't know VS Extensions well enough to diagnose!
The text was updated successfully, but these errors were encountered: