Skip to content

Commit 88c174f

Browse files
author
Mohith Shrivastava
committed
release 0.3 version
1 parent d9ed7ec commit 88c174f

File tree

11 files changed

+59
-2
lines changed

11 files changed

+59
-2
lines changed

CHANGELOG.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,34 @@
11
# Change Log
22
All notable changes to the "dx-code-companion" extension will be documented in this file.
33

4+
### 0.3.0
5+
6+
Fully support changeset driven development (https://trailhead.salesforce.com/en/content/learn/modules/declarative-change-set-development/develop-and-test-changes-locally)
7+
8+
With this release,you can use DX Code Companion extension to retrieve source from the changeset created in your sandbox (Assumes you have authorized CLI to sandbox using "SFDX:Authorize and org").Use vscode to edit contents if needed and then deploy to target orgs all from VScode without need to upload the changesets and wait.
9+
10+
1) To retrieve source from the changeset use the command pallete and select "CCDX:Retrieve Source From Changeset"
11+
12+
![Retrieve source from changeset](./images/retrieve_changeset.png)
13+
14+
2) Provide the changeset name in the text box (Avoid creating changesets with same name in sandbox)
15+
16+
![changeset name](./images/changesetname.png)
17+
18+
3) Once code components are retrieved , Under changeset directory a sub directory will be created with src folder having all the components .You can edit the source code and also save to the authenticated orgs.
19+
20+
![changeset dir structure](./images/changesetdir.png)
21+
22+
4) Note that the changeset directory has orgs.json to which you can add list of orgs you have authorized salesforce CLI by clicking on the file and using "CCDX:Add Orgs For Changeset Deployment"
23+
24+
![Add orgs for depolyments](./images/addChangesets.png)
25+
26+
5.Click on "src" folder for your changeset to deploy them . The interface will ask you to pick orgs you added in previous step
27+
28+
![Deploy changeset](./images/changesetDeploy.png)
29+
30+
![Select the target org](./images/deployorgselector.png)
31+
432
### 0.2.8
533

634
1. Fixes connection method to use salesforce core library native methods

README.md

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -111,6 +111,34 @@ To open command pallete and look for all CCDX Commands use below .
111111

112112
# Release Notes
113113

114+
### 0.3.0
115+
116+
Fully support changeset driven development (https://trailhead.salesforce.com/en/content/learn/modules/declarative-change-set-development/develop-and-test-changes-locally)
117+
118+
With this release,you can use DX Code Companion extension to retrieve source from the changeset created in your sandbox (Assumes you have authorized CLI to sandbox using "SFDX:Authorize and org").Use vscode to edit contents if needed and then deploy to target orgs all from VScode without need to upload the changesets and wait.
119+
120+
1) To retrieve source from the changeset use the command pallete and select "CCDX:Retrieve Source From Changeset"
121+
122+
![Retrieve source from changeset](./images/retrieve_changeset.png)
123+
124+
2) Provide the changeset name in the text box (Avoid creating changesets with same name in sandbox)
125+
126+
![changeset name](./images/changesetname.png)
127+
128+
3) Once code components are retrieved , Under changeset directory a sub directory will be created with src folder having all the components .You can edit the source code and also save to the authenticated orgs.
129+
130+
![changeset dir structure](./images/changesetdir.png)
131+
132+
4) Note that the changeset directory has orgs.json to which you can add list of orgs you have authorized salesforce CLI by clicking on the file and using "CCDX:Add Orgs For Changeset Deployment"
133+
134+
![Add orgs for depolyments](./images/addChangesets.png)
135+
136+
5.Click on "src" folder for your changeset to deploy them . The interface will ask you to pick orgs you added in previous step
137+
138+
![Deploy changeset](./images/changesetDeploy.png)
139+
140+
![Select the target org](./images/deployorgselector.png)
141+
114142
### 0.2.8
115143

116144
1. Fixes connection method to use salesforce core library native methods

images/addChangesets.png

306 KB
Loading

images/changesetDeploy.png

284 KB
Loading

images/changesetdir.png

29 KB
Loading

images/changesetname.png

109 KB
Loading

images/deployorgselector.png

29.4 KB
Loading

images/retrieve_changeset.png

213 KB
Loading

src/extension.ts

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
// Import the module and reference it with the alias vscode in your code below
44
import * as vscode from 'vscode';
55
import {Config} from './services/config';
6-
import CodeCompanionContentProvider from './providers/ContentProvider' ;
6+
import CodeCompanionContentProvider from './providers/ccprovider' ;
77
import {Changeset} from './services/changeset';
88
import {DeploySource} from './services/deploy';
99
import {NavigationService} from './services/navigation';
@@ -107,6 +107,7 @@ export function activate(context: vscode.ExtensionContext) {
107107
context.subscriptions.push(vscode.workspace.onDidSaveTextDocument((textDocument: vscode.TextDocument) => {
108108
DeploySource.deploy(textDocument);
109109
}));
110+
110111
context.subscriptions.push(deploySource);
111112
context.subscriptions.push(changesetRetrieve);
112113
context.subscriptions.push(compareSource);

0 commit comments

Comments
 (0)