[Bug 0.8.4]: #exec statements are disregarded, cause exceptions, have wrong highlights

[jarcen]

Describe the bug

When trying to import resource like that

#exec AUDIO IMPORT FILE="Sounds\sound.wav" NAME="MySound" GROUP="Misc"

multiple problems occur:

1. I get exceptions starting at typing FILE string. After that they continue in defaultproperties on each keystroke when attempting to use new name. (see below)
2. The newly created name Sound'MySound' is "not found" and pollutes problem list.
3. There is an attempt to highlight escape codes like "\b", "\t" or "\s". UCC does not try to escape characters when processing these string, they should not be highlighted.

An error was thrown while parsing document: "file:///c%3A/UnrealTournament/MyPackage/Classes/MyClass.uc" Error: cannot consume EOF
    at wm.consume (c:\Users\User\.vscode\extensions\eliotvu.uc-0.8.4\out\server.js:48:15801)
    at t.skipLine (c:\Users\User\.vscode\extensions\eliotvu.uc-0.8.4\out\server.js:166:23996)
    at t.directive (c:\Users\User\.vscode\extensions\eliotvu.uc-0.8.4\out\server.js:166:33136)
    at t.member (c:\Users\User\.vscode\extensions\eliotvu.uc-0.8.4\out\server.js:166:35315)
    at t.program (c:\Users\User\.vscode\extensions\eliotvu.uc-0.8.4\out\server.js:166:33730)
    at YR.build (c:\Users\User\.vscode\extensions\eliotvu.uc-0.8.4\out\server.js:352:44604)
    at eO (c:\Users\User\.vscode\extensions\eliotvu.uc-0.8.4\out\server.js:352:51703)
    at Object.next (c:\Users\User\.vscode\extensions\eliotvu.uc-0.8.4\out\server.js:370:11777)

Also I wish there was a way to completely disable checks for resources, both relative like Sound'MySound' and absolute Sound'UnrealI.Skaarj.Land1SK'. I know there is package indexing but it shouldn't be required to have game files just to write code. Disabling this altogether would be an easy and quick fix for massive pollution of problem list, especially when right now it doesn't work correctly.

Screenshots

[jarcen]

The "cannot consume EOF" error seems to be more general and I get it constantly when creating new file and starting typing class keyword.

[EliotVU]

Those typing errors appear to have already been fixed along with some re-factoring of the code base, i.e. migration from antlr4ts to antlr4ng;

Yeah, a disable option might be in scope (should probably only report errors for Class types)

I just polished some of the syntax highlighting:

Thoughts?

[jarcen]

Yeah, looks good. IMO merging # symbol into #exec highlight would look better.