Improved Apex Language Support for ".apex" execute anonymous files

Summary

When writing Apex in a .apex file to be used for anonymous execution, the Apex language server marks the first line of code as invalid with an “Unexpected token” error. It seems the language server expects a class or trigger keyword and does not know what to do with simple lines of Apex outside that context.

Steps To Reproduce:

1. Create an .apex extension file inside a dx project
2. Write a single line of apex like so: System.debug('Hello World');

Expected result

No error message appears in the “Problems” output panel.

Actual result

The following error message appears in the “Problems” output panel: Unexpected Token: 'System.debug'. (1,1).

Additional information

VS Code Version: 1.23.1

SFDX CLI Version: 6.17.0-b1f53723b9

OS and version: macOS High Sierra 10.13.4

[vazexqi]

@ntotten - Yes, we need to make changes to the Apex LS to make it understand execute anonymous – I don’t think it’s big but it needs to be done.

As you can see in the screenshot above in the issue, the LS is saying there is an error in that file. That’s because it’s treating .apex as a .cls file and the only top-level constructs allowed in a .cls file are class|enum|interface declaration. You cannot have standalone statements like you can with execute anonymous.

I’m not opposed to doing this. I just want to know if .apex is the extension convention that we want to adhere to. It’s not documented anywhere in our docs.

[smaddox-sf]

Belatedly closing this. The original issue has been resolved.