Use the Apex extension for VS Code to access code-editing features such as code completion, go to definition, view outlines of Apex classes and triggers, refactoring, and find syntactic errors in your code.
The Apex extension provides context-sensitive suggestions when you’re working in an Apex class or trigger. As you type, auto-completion lists members such as methods or variables. The auto-completion list also displays the documentation for the suggestions. Use these keys:
To change how suggestions are pre-selected, see IntelliSense - Suggestion selection.
Code snippets are available for scaffolding class and interface definitions, and a variety of statements, such as loops and conditional statements. When you’re working in an Apex class or trigger, run Insert Snippet from the Command Palette to view the available snippets. You can also view these code snippets as code completion suggestions.
Out of the box snippets for Salesforce development are available in these repositories:
The real power of snippets comes with customizing snippets for your own use. Follow these steps to create a custom Apex snippet that lets you quickly write a simple SOQL query:
Run the Snippets: Configure User Snippets command from the Command Palette.
Select apex.json to open the file.
Add this snippet code to the file:
1"SOQL" : {
2 "prefix": "soql",
3 "body": [
4 "[SELECT ${1:field1, field2} FROM ${2:SobjectName} WHERE ${3:clause}];"
5 ],
6 "description": "Apex SOQL query"
7 }Save the file.
Use this snippet in your Apex class file by typing “soql” and selecting to add this snippet to your code.
The code snippet [SELECT field1, field2 FROM SobjectName WHERE clause]; is added to your Apex file.
For more information about snippets, see Snippets in Visual Studio Code.
In addition to the generic snippets feature available in VS Code, you can use custom templates to create metadata for an Apex class or trigger. Here’s an example of using a template for your Apex classes:
DefaultApexClass.cls file with your custom code:1//Copyright (c) <year><copyright holder>
2
3public with sharing class <%= apiName %> {
4 public <%= apiName %>(String prop) {
5 this.prop = prop;
6 }
7 @AuraEnabled
8 public static List<SObject> getRecords(){
9 try {
10 return [Select Id from Sobject];
11 } catch (Exception e){
12 throw new AuraHandledException(e.getMessage());
13 }
14 }
15}ApexClass for filename.Confirm that the ApexClass.cls file contains your custom code.
To ensure that the Intellisense feature correctly prompts completion suggestions, you must refresh the SObject definitions. Run the SFDX: Refresh SObject Definitions command from the Command Palette.
You can now preview, view, or go to definitions of:
When you refresh SObject definitions, the extension uses the default org to generate Apex classes. These classes represent the standard and custom objects that the current user has access to. We recommend that you don’t edit these representative Apex classes because these classes are intended to be read only. If they’re modified, it may impact the auto-completion suggestions. Also, the changes are lost when you refresh the SObject definitions.
Whenever you refresh SObject definitions, the representative Apex classes are deleted and regenerated. You can modify the SObjects either by updating the objects’ .object-meta.xml and .field-meta.xml files; Or by making changes declaratively in the default org. After modifying the SObjects, make sure to sync your local project and the default org.
When you launch the Salesforce CLI Integration extension (which is part of the Salesforce Extension Pack) for the first time and the salesforcedx-vscode-apex.enable-sobject-refresh-on-startup setting is enabled, SFDX: Refresh SObject Definitions command is executed automatically if your project doesn’t contain any Apex classes. After you add or edit standard or custom objects or their fields, make sure to run this command.
Apex extension provides go to definition support for user-defined Apex such as classes and methods, standard objects, and custom objects.
You can find all references to user-defined Apex such as classes, class variables, enums, interfaces, methods, and properties. To find references, right-click the item and select Go To References or press Shift+F12; Or right-click the item and select Find All References. The reference results are displayed in the left pane of the editor window.
The Apex outline view shows the structure of the Apex class or trigger that’s open in the editor.
The Explorer in the Side Bar also provides an Outline view to assist you while working on your project.
Any syntax errors such as a missing semicolon or a bracket are marked with a red squiggly line in the editor. The Problems panel also lists the syntax errors. To go to the source file with the syntax error, double-click the error.
When you reference a method that isn’t declared in your source, use the Quick Fix widget to automatically declare the method.
Declare Missing Methods quick fix can be invoked in the following ways:
The keyboard shortcut for the Quick Fix widget is Cmd+ in macOS and Ctrl+ in Windows and Linux.
Note
It’s common to keep Apex code in your project for executing certain tasks. By default, a new project has a folder scripts/apex that contains an example hello.apex file. We recommend that you use this folder to create your Anonymous Apex files using the .apex file extension.
You can execute Anonymous Apex in Visual Studio code in two ways:
In both cases, the result of the executed code is printed to the output pane.
It’s common to keep Apex code in your project for executing certain tasks. By default, a new project has a folder scripts/apex that contains an example hello.apex file. It’s recommended that you use this folder to create your Anonymous Apex files using the .apex file extension.
j