VSCode listenable() verse errors after 35.00

Summary

There are VSCode (in editor only) errors connected to listenable() inthe 35.00 release. These cascade to further errors in the project which makes working really annoying. The error is the good old “Can’t access a function from a preceding type”

The errors do not show up in regular compilation step.

Those of us who were unlucky enough to try to implement own listenable have a really bad time

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Steps to Reproduce

  1. Create a pristine new project, check the Verse.digest
  2. Notice the errors in Verse.digest
  3. Make a function that expects e.g. a response from a listenable.
  4. Sob silently because of broken in-editor experience

Expected Result

No verse in-editor errors in digest files

Observed Result

verse in-editor errors in digest files

Platform(s)

All

Upload an image



Was reported but not a s a bug previously:

Thank you @VerySpicyGames for the report.

Another thread here: Blocks in Race giving errors

FORT-899874 has been added to our ‘To Do’ list. Someone’s been assigned this task.

@Flak @Vath

Good morning, Hope all is well

Do you have a rough idea of when this will be fixed ?

I have put off verse due to this issue but i am now having to do versing and this is the most annoying visual thing ever imo. Its personally driving me crazy :frowning:

can we not have a version that doesn’t have a million visual issues as trying to develop games like this is extremely frustrating.

Thankyou for taking the time to read this.

This is what i mean…

Every script near enough including epic ones are just full of squiggles

2 Likes

Hi im new and on my first time use ever I had this same issue I did nothing it came out the gate like this any fix?

I’m having the same issue :frowning:

An update:
in 35.10 the red squigglies seem to be gone, but the type information is not available in the affected files:

1 Like

Restart everything mine works and shows the input trigger but i havnt tested the item granter

Tested… @VerySpicyGames

Its a huge improvement for sure

Only a few left now