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

Fully qualified yarn commands don't get detected by the LSP #376

Open
McJones opened this issue Oct 12, 2023 · 1 comment
Open

Fully qualified yarn commands don't get detected by the LSP #376

McJones opened this issue Oct 12, 2023 · 1 comment
Labels

Comments

@McJones
Copy link
Collaborator

McJones commented Oct 12, 2023

If you fully qualify the YarnCommand attribute (so [Yarn.Unity.YarnCommand("do_a_thing")] instead of [YarnCommand("do_a_thing")]) even though this works fine in Unity the LSP doesn't correctly link this in the editor.

This means you get warnings about the command even though it works fine.
As a workaround you can import Yarn.Unity and then use the shorter form.

@McJones McJones added the bug label Oct 12, 2023
@McJones
Copy link
Collaborator Author

McJones commented Nov 24, 2023

this also impacts fully qualified functions using the YarnFunction attribute

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant