Improve Apex Autocomplete

Summary

When Autocomplete is run on an SObject, it returns Global objects (EG System, ApexPages), which are not valid given the current instance context. It also only returns a very limited set of fields.

Steps To Reproduce:

1. Create new class call testing
2. Add the following code:

public class Testing {
    public Testing() {
        Account acc = new Account();
        acc.
    }
}

1. Trigger a completion request on acc.

Expected result

I would see the SObject Instance methods and all of it’s fields (including custom fields)

Actual result

I see the SObject instance methods, the global System namespaces & and very limited set of fields.

Additional information

VS Code Version: 1.26.0

SFDX CLI Version: salesforcedx@pre-release

OS and version: osx 10.12.6

[ChuckJonas]

Adding to the List…

I can’t seem to get static variables and functions to auto-complete either.

IMO the lack of decent auto-complete really is the biggest productivity killer.

Is there a team working on this? I understand the challenging of building AST, but other multiple other individuals have been able to do a pretty decent job of it…

Seems like a company as big as salesforce should be able to figure out how to write autocomplete for their own language pretty easily

PS: I’m not trying to be snarky, I’m just sincerely wondering this issue is a priority.

[vazexqi]

@ChuckJonas -

[Context] " it returns Global objects (EG System, ApexPages)" – yes this is a known issue right now. We show a lot of the global namespaces as a fallback. We should probably disable this.

[SObjects] Did you do a “SFDX: Refresh SObject Defintions” after you have connected to an org? See https://github.com/forcedotcom/salesforcedx-vscode/tree/develop/packages/salesforcedx-vscode-apex#enable-code-smartness-for-sobjects for more information.

We need to do an sobjectdescribe on the org to get the information – yes, this deviates a bit from our SFDX model but the org currently still has the most information about the standard objects, custom fields, and custom objects.