ForceCode

Overview

This extension is a companion for SFDC (Salesforce.com) development with ,.
It is targeted at developers who want a lightweight and fast way to work with their Salesforce files.
There's no complicated setup process or project configurations, no external apps to keep open, and no jarring errors knocking you out of your flow.

Important

You will need to install the SFDX-CLI on your system in order for this extension to function! Please download from https://developer.salesforce.com/tools/sfdxcli and install, then restart Visual Studio Code.

Slack

ForceCode now has a Slack channel! Join us - https://join.slack.com/t/forcecodeworkspace/shared_invite/enQtOTMwMjkwODQwNzA0LThhNWJlNDA0OTg3OWFmN2YyNzEwNTdlNzA3ZGJhODc5YWI2MTBjODY2YTFmMzE0YjZjOWUyMGMyZTY5YzVmMDU
Use this to ask question and receive updates on upcoming features!

Permissions

Please note that the following permissions are required to develop on the Force.com platform: https://developer.salesforce.com/docs/atlas.en-us.pages.meta/pages/pages_intro_permissions.htm

Features

• Ability to create and work in SFDX projects/source format or in the classic Metadata format.
  • You will be asked for the format to use when creating a new project. Existing projects will continue to support the Metadata format.
• For code completion and highlighting I highly recommend downloading the various Salesforce language server extensions.
  • Follow the installation instructions on the Apex Code Editor page (You must install the Salesforce CLI for code smartness to work!)
  • For apex code completion, select code completion refresh from the ForceCode menu and it will work with the Salesforce apex language server extension. You will need to refresh for each org. ForceCode handles the rest and switches code completion files when switching orgs/usernames.
• Edit and save almost everything in Salesforce textually (Workflows, classes, lead assignment rules, etc..)
  • Now works with the autoCompile option. Save the file and Salesforce will send it to the org (If this option is on).
• View save history results for x number of saves (maxSaveHistory setting) and view any error messages from the save by hovering over the save result (Filename of the save)
• Right-click on a file in the explorer to save.
• Right-click on a file or folder to refresh from the server.
• Multiple org support. Log into each org through ForceCode and you won't need to log out to switch orgs, simply click on another org in the "Saved Usernames" view and ForceCode will log you in.
  • You can now right-click on a username to switch/login/logout of an org. When logging out using this method you don't need to switch to the org you're logging out of.
• Open Classes, Triggers, Visualforce pages, and Visualforce components by right-clicking and selecting the open file in org.
• Simple graphical settings editor.
  • Allows for settings for each org.
• Open org in the browser. No more need to open a browser and log in to salesforce.
• Preview Visualforce pages/Lightning apps.
  • Either right-click and select preview or click the icon that appears in the upper right.
• Task view. See what ForceCode is up to and execute multiple commands at the same time.
• Code Coverage view. Will show the coverage on files open in your project.
  • You can even have this view revealed after running an apex test.
  • Breaks down coverage by classes with sufficient/insufficient coverage.
  • Shows which classes/methods are covering your class
    • Click on each to update line decorations for a visual representation of coverage provided by each test class/method.
• Retrieves code coverage on the startup of the extension.
• Search in files. Works just like the developer console search in files feature.
• Retrieve org-wide code coverage. This will show up in a file with all apex classes and their coverage listed.
• Auto comparison of file changes on load/save. Will also show the last person's name that changed the file.
• NO MORE PASSWORDS SAVED IN THE CONFIG FILE!!!
  • Login through the browser and you will be auto-logged in through ForceCode every time until you log out.
• Save / Compile / Deploy a file
  • Works with Classes, Triggers, Components, Pages, Permission Sets, Objects, Custom Labels, and Lightning Components
  • Provides line errors in the editor
  • Works great with autosave
• Delete metadata from the org
  • Currently, delete functionality is limited only to certain metadata (All metadata that can be created via the New menu option is supported and a few others). If you receive an error stating that the metadata wasn't found in the org and you are sure it is indeed there, then the type is not currently supported for deletion by Forcecode
  • Aura component pieces can be removed individually or as a whole. If you delete the Aura component's cmp, app, etc file or the -meta.xml file then the whole bundle will be removed from the org. When deleting an LWC, the whole bundle will ALWAYS be removed!
• Run Unit Tests
  • Hover over @isTest or testMethod to get a link to run the test class or method
  • Code coverage highlighted in the editor
  • Coverage warnings and percents
  • Errors in the editor on test failures
  • Auto-open test log (If there is output, based on the filter)
  • Easy to run a single tests or all tests in a Class
• Execute Anonymous
  • Highlight text, then right-click and select "Execute Anonymous" or select "Execute Anonymous" from the ForceCode menu
• View / Save Debug Logs (Use the menu item to get debug logs to save)
• Open / Retrieve a file
  • Works with Classes, Triggers, Components, Pages, Static Resources, and Lightning Components
  • Multiple files can be selected to open from the server.
• Deploy Package
  • You can now choose files in your current org folder to deploy and ForceCode will build a package.xml file and deploy the files!
  • Replaces need for CumulusCI w/ Ant
  • Retrieve detailed deploy information
  • ForceCode now only deploys the files contained in your package.xml! (Yes, destructiveChanges.xml, destructiveChangesPre.xml, and destructiveChangesPost.xml files will deploy as well so be careful!!!)
• Retrieve Package
  • Retrieve all metadata
  • Retrieve by selecting from available Packages
  • Retrieve by package.xml
  • Retrieve by selecting types
  • Retrieve all classes
  • Retrieve all pages
  • Retrieve all aura definition bundles (Lightning components, events, apps, etc)
  • Retrieve all custom objects
  • Retrieve all standard objects
• Bundle & Deploy Static Resources on save
  • Auto-refresh the browser on save (Mac only)
  • Works great with autosave
• Create Aura components, classes, LWC components, triggers, and Visualforce pages/components
• Diff server & local versions
• SOQL and Tooling query editor
  • Quickly run SOQL Queries
  • Query Tooling Objects
  • Results displayed in a table
  • Results can be saved as JSON or CSV (if outputQueriesAsCSV is checked)
  • Inline edits can be made in the results table (Just like in the developer console)
• Arbitrary folder structure
  • Change your project src folder
  • Flexible project structure
• API Limit Warnings (Now a hover, when you hover over usernames in the Saved Usernames view (This also shows the project's path))
• Perform bulk record updates with CSV files (Insert, update, upsert, delete, hard delete)