Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Variable/Function completion no longer works in <<if>>, <<set>> commands #47

Open
fmoo opened this issue Feb 17, 2024 · 0 comments
Open
Labels
bug Something isn't working

Comments

@fmoo
Copy link

fmoo commented Feb 17, 2024

What is the current behavior?

When writing an <<if>> or <<set>> statement, the vscode extension no longer suggests variables or custom functions.

Please provide the steps to reproduce, and if possible a minimal demo of the problem:

Type the following commands into any node:

<<declare $foo = 0>>
<<if $

Or:

<<declare $foo = 0>>
<<set{space}

(where {space} is a trailing spacebar keystroke)

What is the expected behavior?

The plugin should suggest valid variable names and custom functions.

Please tell us about your environment:

  • Yarn Spinner Version: 2.3
  • Extension Version: 2.2.113 or newer
  • Unity Version: 2021.3.25f1

Other information

  • Variable/Function suggestions work just fine inside of {...} braces inside of regular custom <<Commands>>
  • Versions 2.2.113 or older behaved as expected wrt: code completion on if and set statements
@fmoo fmoo added the bug Something isn't working label Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant