Development

The Dev section of codev is where day-to-day Salesforce development happens: getting a development org, seeing what changed in it, retrieving those changes into your project as source, and committing, validating, and raising pull requests.

Development runs in the codev desktop app. When you open a project, the app keeps a local working copy of your repository — your workspace — checked out on a branch on your machine. The pages under My Workspace work against this local copy, so the workspace pages described here are available on desktop. Workspace Explorer and Org Explorer also exist in the web app as read-only variants — noted in their sections below.

Before you start

• The codev desktop app, signed in and connected to your codev server, with your project open.
• A development org assigned to you. You fetch one from a pool — see Fetching and using environments.

Finding your way around

The home page, My activity, summarises your open pull requests, review environments, and the dev sandboxes you hold.

The Dev section in the sidebar is organised into groups:

• My Orgs — the orgs currently assigned to you (Assigned to Me) and a browser for the metadata of any connected org (Org Explorer).
• My Workspace — your local copy of the project: Workspace Explorer to browse and edit source, Org Changes to see what changed in your org, and Source Control to commit, sync, and validate.
• Modularize, Review, Testing — the project's domains and packages, validation reports and pull requests, and Apex test runs.

The development workflow itself — from getting an org to raising a pull request — is covered step by step in Development workflow.

The status bar

The bar at the bottom of the window holds two controls the whole Dev section depends on.

• The branch button shows the branch your workspace is on. Click it to switch to another local branch, or type a new name to create one.
• The org button shows your target org. Every org-facing action uses it: the Org Changes list, retrieves, deploys, and Apex test runs. Click it to pick another connected org — orgs are grouped into DevHubs and sandboxes, and the current target is marked.

The right side shows the server you are connected to, the state of the last operation, background tasks, and the console.

Workspace Explorer

Workspace Explorer shows your project's source, one tree per package directory. Inside a package, files are grouped by metadata category and type — for example Data model > CustomObject > Account > CustomField — rather than by folder, and each package shows the domain it belongs to.

Click a file to open it in the editor. Salesforce metadata files have two view modes, switched from the toolbar: Metadata, a structured form of the parsed file, and XML, the raw source.

Hovering a file shows three org actions — Compare (diff the file against an org), Pull (retrieve it from an org), and Push (deploy it to an org). Each opens an org selection dialog with your target org preselected. Hovering a package offers Push package and the package's settings.

Right-click actions

The context menu on a file carries the full set of workspace operations, grouped: opening (Open File, Open in VS Code, Get Usage, Analyze Code), the org actions (Compare with Org, Push to Org, Pull from Org), restructuring (Move to Package, Move to Destructive, Convert to Aliasfy), Add to Force Ignore, file-system operations, and tags.

The menu adapts to what you clicked. A package's menu offers Edit Package, Push Package, code analysis, string replacement, aliasfy management, and file-system operations such as Create New Metadata; a Profile adds Reconcile Profiles; a Flow adds View Flow; files in a data package hide the org and restructuring actions.

Org Explorer

Org Explorer browses the metadata of the target org itself — everything in the org, not just what is in your project. The first time you open it for an org, run Sync to build the org's metadata inventory; the sync runs in the background and notifies you when it completes.

From the tree you can:

• Click a component to retrieve its content and open it in the editor.
• Select components with the checkboxes and retrieve them into a package — each row has a Package selector for the destination package directory.
• Compare with local to diff an org component against your workspace copy.

Right-click actions

A component's context menu offers Compare with Local, Get Usage (where the metadata type supports usage analysis), and Copy Name; Profile components add Reconcile Profiles. Opening the org and bulk-retrieving the selection sit in the tree's toolbar rather than the menu.