VSCode is not recognizing verse properly in v43.00

[rhyan.smith (Rhyan)]

Hi, thanks for reporting this!

We have already received this report and is a known issue

@rhyan.smith

Verse: false errors on Await() for events in Visual Studio Code

In 43.00, Visual Studio Code may show errors when you call Await() on an event or a listenable, for example Interactable.SucceededEvent.Await(). You may see:

• Unknown member Await in listenable(agent)
• Invalid access of internal function (/Verse.org/Verse/event:)Await
• All the top level expressions in a ‘race’ macro must be async
• We’re investigating now

The VS Code Verse extension shows incorrect errors when you call Await() on an event or listenable, for example Interactable.SucceededEvent.Await(). Errors include Unknown member Await in listenable(agent) and Invalid access of internal function (/Verse.org/Verse/event:)Await. Your Verse code still compiles and runs correctly in UEFN, so these errors can be ignored.

Using awaitable::Await causes invalid errors

Summary When using awaitable::Await() the Verse LSP will incorrectly flag it as an error. Please select what you are reporting on: Verse What Type of Bug are you experiencing? Verse Steps to Reproduce Use awaitable::Await() e.g. Interactable.SucceededEvent.Await() Expected Result The Verse LSP doesn’t flag it. Observed Result The Verse LSP flag an error. Invalid access of internal function (/Verse.org/Verse/event:)Await from control scope Unknown member Await in listenable(agent). All t…

I’m going to close this thread out as it’s a duplicate, if you have any follow ups please use the above thread