You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: messages/dev.generate.command.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Generate a new sf command.
6
6
7
7
You must run this command from within a plugin directory, such as the directory created with the "sf dev generate plugin" command.
8
8
9
-
The command generates basic source files, messages (\*.md), and test files for your new command. The Typescript files contain import statements for the minimum required Salesforce libraries, and scaffold some basic code. The new type names come from the value you passed to the --name flag.
9
+
The command generates basic source files, messages (\*.md), and test files for your new command. The Typescript files contain import statements for the minimum required Salesforce libraries, and scaffold some basic code. The new type names come from the value you passed to the --name flag.
10
10
11
11
The command updates the package.json file, so if it detects conflicts with the existing file, you're prompted whether you want to overwrite the file. There are a number of package.json updates required for a new command, so we recommend you answer "y" so the command takes care of them all. If you answer "n", you must update the package.json file manually.
12
12
@@ -26,6 +26,10 @@ Generate a unit test file for the command.
26
26
27
27
Name of the new command. Use colons to separate the topic and command names.
28
28
29
+
# flags.dry-run.summary
30
+
31
+
Display the changes that would be made without writing them to disk.
32
+
29
33
# examples
30
34
31
35
- Generate the files for a new "sf my exciting command":
0 commit comments