Starting at version 3.9.6, ForceCode supports per-org settings (Which can be changed via the settings menu option). If you don't want your settings reset then take a backup of your force.json file as a reference and change the settings via the settings menu option for each org. 3.9.6 and up will no longer support the srcs option and the srcDefault option, as they are no longer needed. Your settings will be preserved when you log out of an org for the next time that you log in. The force.json file is now only used to hold the last logged in username, so do not edit this file. Settings are now stored in settings.json files in the .forceCode folder in each username folder.
The extension has changed tremendously between versions 3.7.1 and 3.8.0. Please read the below information for changes before submitting an issue because you think something doesn't work! The contents of this README have changed quite a bit, so pay attention. Before we get into details, if you're wanting to upgrade to 3.8.0 then there are a few things you need to do to "convert" the project:
First or all, you don't need the wsMembers.json file anymore! ForceCode now uses file last modified dates to compare for changes!
- Create a new project in an empty folder logging into the org who's project you want to convert. First thing you will notice is you don't need to input a username into ForceCode, this is because it will grab it from the result of logging in through the browser.
- As stated previously, the force.json file is no longer used to hold settings information. Settings can be modified via the settings option in the menu.
- Open the old and new projects in a file explorer and copy (or cut) everything out of your src folder and paste it into the new project's src folder for that org.
- The "resource-bundle" folder (If applicable) needs to be copied into the new project's src folder (NOT THE ROOT LIKE THE OLD PROJECT). Any SOQL, TOQL, or coverage folders can be copied into the src file as well (If desired).
- If you don't mind refreshing sObjects for code completion over again for each org then you are done. Skip this step and read on. If you don't want to refresh your code completion sobjects then go back to the project root of each project (the folder containing the force.json) and copy the .sfdx from the old project into the .forceCode/(USERNAME HERE)/.sfdx folder. You're all set now, read on for more info!
This extension is a companion for SFDC (Salesforce.com) development with Visual Studio Code.
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.
ForceCode now has a Slack channel! Click here to join us! Use this to ask question and receive updates on upcoming features!
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
- For code completion and highlighting I highly reccomend 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).
- 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 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 login to salesforce.
- Preview Visualforce pages/Lightning apps.
- Either right click and select preview or click the icon that appears in the upper right.
- Run Salesforce CLI commands (DX in the menu)
- 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.
- Retrieves code coverage on 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
- Run Unit Tests
- Hover over @isTest or testMethod to get a link to run the test class or method
- Code coverage highlighting 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"
- 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 Classes from templates
- Diff server & local versions
- SOQL and Tooling query
- Quickly run SOQL Queries
- Query Tooling Objects
- Results are returned as JSON or CSV (if outputQueriesAsCSV is set to true (checked))
- Arbitrary folder structure
- Change your project
srcfolder - Flexible project structure
- Change your project
- API Limit Warnings (Now a hover, when you hover over usernames in the Saved Usernames view (This also shows the project's path))
- Why do I receive an error that says 'ForceCode.showMenu' failed?
- You must open a folder in the VSCode workspace before trying to connect with ForceCode.
- Why do I get an error when trying to login about a localhost connection failure?
- This means your network is either on a proxy or vpn and you will need to go here to set up Forcecode to work with this type of connection.
Before submitting an issue, please read the FAQ section above to make sure that your issue isn't answered already. Please submit any issues or feature requests to https://github.com/celador/ForceCode/issues
You need to have a folder opened in VSCode to be able to start this extension!
To begin, press Opt+Cmd+C or open the Command Pallet and type >ForceCode: Menu to bring up the ForceCode Menu
You can then select if you want to log into a production org or test org. A browser will then open to the Salesforce login where you can enter your credentials. A configuration file will then be auto generated for you for each of your orgs in the .forceCode folder called settings.json.
The configuration file will look like the following. You can either edit this file to change the settings or you can use the settings option in the ForceCode menu (Recommended)!
{
"apiVersion": "44.0",
"autoCompile": true,
"autoRefresh": true,
"browser": "Google Chrome Canary",
"checkForFileChanges": true,
"debugFilter": "USER_DEBUG|FATAL_ERROR",
"debugOnly": true,
"deployOptions": {
"allowMissingFiles": true,
"checkOnly": false,
"ignoreWarnings": true,
"purgeOnDelete": false,
"rollbackOnError": true,
"runTests": [],
"testLevel": "NoTestRun"
},
"outputQueriesAsCSV": false,
"overwritePackageXML": false,
"poll": 1500,
"pollTimeout": 1200,
"prefix": "",
"revealTestedClass": false,
"showFilesOnOpen": true,
"showFilesOnOpenMax": 3,
"showTestCoverage": true,
"showTestLog": false,
"spaDist": "dist",
"src": "src",
"staticResourceCacheControl": "Private",
"username": "MonsterMike@Salesforce.com",
"url": "https://login.salesforce.com"
}- apiVersion: This is the default api version that all your files will be saved with. If this is not set, this will default to the version of the org in use. ForceCode will not change the version of an existing file. This is also the version used for package retrieval and deploy.
- autoCompile: When a supported file is saved (works with VSCode's autosave feature) the file is saved/compiled on the server. Otherwise, use
cmd + opt + sto save the file to the server. - autoRefresh: If autoCompile is on, and you're working in a resource-bundles folder, the staticResource will automatically compile and deploy to your org. If autoRefresh is on (and you're working on a Mac), the currently active tab in Google Chrome Canary (or your configured browser) will be refreshed. This provides a simple browsersync-like experience without the overhead of browsersync
- browser: Define which browser you want to reload when the static resource refreshes (this only works with Macs at the moment)
- checkForFileChanges: This option, when set to true, will allow ForceCode to check for file changes against the server on startup of ForceCode.
- debugFilter: A regular expression used to match a line for display. The default is to show debug and error lines, so you can filter out the log noise.
- debugOnly: When executing anonymous, we can either show all the output or only the debug lines. This makes it easier to debug your code. Turn if on for the important stuff, and turn it off to get all the detail.
- deployOptions: Deploy your package based on your configured deploy options and the package.xml in your src folder.
- allowMissingFiles: Specifies whether a deploy succeeds even if files that are specified in package.xml but are not in the .zip file or not.
- checkOnly: Validation only deploy. Don't actually deploy your code, just make sure it all compiles as a package.
- ignoreWarnings: Indicates whether a warning should allow a deployment to complete successfully (true) or not (false).
- purgeOnDelete: If true, the deleted components in the destructiveChanges.xml manifest file aren't stored in the Recycle Bin.
- rollbackOnError: Indicates whether any failure causes a complete rollback (true) or not (false)
- runTests: A list of Apex tests to run during deployment (commma separated list)
- testLevel: Specifies which tests are run as part of a deployment Options are: NoTestRun / RunSpecifiedTests / RunLocalTests / RunAllTestsInOrg
- outputQueriesAsCSV: if set to true, will retrieve soql/toql results in csv form. If false, json will be returned
- overwritePackageXML: if set to true, will overwrite package.xml file upon opening or retrieving files
- poll: When compiling, this is the interval (in milliseconds) at which we poll the server for status updates. This is only applicable to Classes, Pages, Triggers, and Components.
- pollTimeout: When retrieving packages, or other long running tasks, this is the maximum amount of time (in seconds) it will wait before the process times out. If you're having trouble retrieving your package, try increasing this number. Default is 600 (10 minutes).
- prefix: This is the namespce prefix defined in your package settings for your org. Set this if you have a namespaced org. Otherwise ForceCode will attempt to infer a prefix from your Salesforce Org. If you have a namespaced org and do not set this setting, you may have problems, especially if working on an out of date Org. This should be automatic as of Salesforce 38
- revealTestedClass: When set to true, this will reveal the class (In the code coverage view) that received the highest amount of coverage from running a test. I say this because if you don't have the tested class in your src folder then it will show the next highest covered class in your project. If none are found then it won't be revealed.
- showFilesOnOpen: If set to true, will open files in the editor when opened from Salesforce
- showFilesOnOpenMax: The maximum number of files to open in the editor. More than 3 usually causes problems or doesn't work.
- showTestCoverage: This flag determines if Apex code coverage highlighting should be shown or hidden in the editor. This can be toggled for the open editor by clicking the colorful icon in the editor bar.
- showTestLog: This flag determines if the Log file for the last test run should show up after the tests are complete. This is nice for debugging tests. Use this in conjunction with the other debug flags to keep your output tidy. The log file will only show if it's not empty (Because of filtering).
- spaDist: When working with SPAs we usually have a "distribution" folder where we build our files to. If this string is set, and a SPA is bundled and deployed, this folder will be used as the distribution folder, otherwise the spa project will be deployed.
- src: This will tell ForceCode where to store the project files for this org.
- staticResourceCacheControl: You can select Public or Private and your static resources will save with the cacheControl set to what this option is set to.
- username: DO NOT TOUCH THIS
- url: DO NOT TOUCH THIS
There's also one special configuration option that's not included in the settings.json, but rather in your vscode settings.json file. This reasoning for separating the files is for portability reasons; to make it easier to share this configuration with others and yourself across projects.
If you open up your settings.json file, or go to Code > Preferences > Workspace Settings and create a new preference, starting with force you should see the filesExclude preference.
This property allows you to have certain files ignored (exluded) from Static Resources when bundled/deployed. This allows you to create a modern SPA project in a "spa" folder instead of keeping it in your "resource-bundles" directory.
However, when we build these SPAs we generally have a ton of preference and source files that we don't want to deploy to Salesforce, both for security and size reasons.
So, you can create Node glob patterns to ignore. The default configuration is shown below.
Glob patterns can be tricky... so a little research and trial and error may be required to get your bundle just right.
{
".gitignore": true,
".DS_Store": true,
".org_metadata": true,
"**/*.map": true,
"node_modules/**": true,
"bower_modules/**": true,
"**.tmp": true,
"**/*-meta.xml": true,
".log": true
}ForceCode provides a number of commands to work with your Salesforce org and metadata.
Menu: >Force: Save/Deploy/Compile
Mac: alt + cmd + s
Win: ctrl + shift + s
To automatically compile/save your changes to Salesforce when the file is saved locally, you can set the autoCompile setting to true.
Otherwise, you will need to use alt + cmd + s to save/compile your file.
To get code completion and errors as you type you will need to install the Salesforce language server extensions for Apex, Visualforce, and Lightning. Forcecode will create sObjects for use with the Apex extension for code completion (smartness as they call it now)
Simply hover over an @isTest or testMethod and you will see a ForceCode hover appear. Follow the instructions given and wath the magic happen!!
Manu: >Force: Execute Anonymous
Mac: alt + cmd + e
Win: ctrl + shift + e
Simply select the code that you want to run, then right click and select Execute Anonymous!
Menu: >Force: Get Class, Page, or Trigger
Mac: alt + cmd + o
Win: ctrl + shift + o
Menu: >Force: Save/Deploy/Compile
Mac: alt + cmd + b
Win: ctrl + shift + b
You can also save a file in a resource-bundle folder and it will deploy
ForceCode looks for Static Resources in two places. The first is resource-bundles, the second is spa. Typically, static resources go in the resource-bundles folder, and the resource is named something like foo.resource where foo is the name of the static resource.
So, to create a new Static Resource, ensure the resource-bundles folder exists in the src folder of your project. Then create a new folder named how you want your static resource to be named with .resource.RESOURCETYPE at the end of the name(E.G. bootstrap.resource.application.x-zip-compressed). IF YOU ARE DEPLOYING A SINGLE FILE, SUCH AS A JAVASCRIPT FILE, THEN THE FOLDER NAME NEEDS TO BE EXACTLY THE SAME AS THE JAVASCRIPT FILE (E.G. myResource.resource.application.javascript will be the folder name and myResource.js will be the only file that can live in this folder!!!!!!!!!!!!!!!!!!!!!!!!!!) If you do it any differently then simply put, it won't work!! You can now Bundle and Deploy this Static Resource.
Whenever you save a file that lives in a resource bundles folder, the resource will automatically bundle and deploy to your org. Use this in conjunction with autoRefresh flag and browser property to get a browsersync-like experience
If you build SPAs, typically you will have a spa folder, then another folder named for your static resource, like spa/foo.
This folder is your Javascript project, where your package.json lives.
You will build your distribution files to a 'dist' folder or another folder determined by the spaDist config property. This folder will live inside spa/foo directory, so you will end up with spa/foo/dist folder structure. One last note, the spa folder NEEDS to be in your src folder!!!
SPA folders do not automatically deploy. We typically run these offline with jsr-mocks and webpack and only deploy when we want to publish.
Menu: >ForceCode Menu ... Deploy Package
Deploy your package based on your configured deploy options and the package.xml in your src folder. ForceCode will now only deploy the files contained in the package.xml file. You now have the option to choose files in your current org folder to deploy and ForceCode will build a package.xml file and deploy the files!If it gives you a deploy error, you're most likely missing at least one -meta.xml file!
Options:
- checkOnly: Validation only deploy. Don't actually deploy your code, just make sure it all compiles as a package. This will generate a
.validationIdfile. - ignoreWarnings: Indicates whether a warning should allow a deployment to complete successfully (true) or not (false).
- rollbackOnError: Indicates whether any failure causes a complete rollback (true) or not (false)
- runAllTests: Runn all tests in org
- runTests: An array of test names to be run [TestClass1, TestClass2,...]
If you want destructive changes as part of the deploy, put a destructiveChanges.xml file in your src folder
Derived from https://jsforce.github.io/blog/posts/20151106-jsforce-metadata-tools.html
Menu: >ForceCode Menu ... Retrieve Package
The apiVersion setting is used to retrieve your package (this setting is important in CI setups) comes directly from your org. When you want to override your Salesforce org version, set the apiVersion setting manually. This is a string, with the decimal.
The pollTimeout setting is used to determine how long you should wait for the retrieve command to complete. This should usually take less than a minute, but can take longer with large packages.
Menu: >Force: Get Logs
Menu: >ForceCode Menu ... Create Class
This will automatically create classes based on apiVersion else it defaults to '44.0'.
SPECIAL NOTE
You can create Classes, Triggers, Components, and Pages by simply creating the file anywhere in your project structure.
When you save it, it'll create the file if it doesn't exist, and update it if it does.
The manual process doesn't automatically create the meta.xml file, so doesn't work seamlessly with CI. However there's no easier way to connect to your org, open a file, modify it and save it back to your org. This means working with multiple orgs is easier than ever.
Open the org in a browser. No more logging in!!
This works just like the "Search Files" feature in the developer console.
This will present to you a list of all the non-foldered types that you want to include in your package.xml. Once you choose the types, you will be asked where you want to save the file. * Reports, documents, etc are foldered and currently not supported
Use this option and ForceCode will create a list of all apex classes and their coverage at the time of retrieval. It will also include an estimated overall coverage percentage (This is calculated by adding up all the other data (covered lines/total lines))
This will grab all sObject data from Salesforce and allow you to use this extension with the Salesforce Apex language extension for code smartness. Make sure you set up the Apex extension correctly by following the instructions here
This will open a ForceCode Settings window where you can change all of the options in your settings.json file in a GUI!
Step 1. Clone this repo to your local machine, like you would with any other Git repository.
Step 2. Open the folder you just created when you cloned the repo in VSCode.
Step 3. Open the terminal by pressing ctrl + ~ and install the dependencies by running npm ci.
Step 4. Press F5 to start debugging the extension. Another VSCode window will open up, which will host your extension. Open your Salesforce project and start working.
Step 5. Find the file for the command you want to run and debug, and put in a breakpoint. Run the command to hit the breakpoint and start exploring the variables.
Step 6. Have Fun!
- The change log has been moved to the CHANGELOG.md file. You should be able to view this information on the extension's home page.