@salesforce/cli 2.23.19 → 2.24.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -6,6 +6,7 @@
6
6
  "cmdt:field:create"
7
7
  ],
8
8
  "args": {},
9
+ "deprecateAliases": true,
9
10
  "description": "Similar to a custom object, a custom metadata type has a list of custom fields that represent aspects of the metadata.\n\nThis command creates a metadata file that describes the new custom metadata type field. By default, the file is created in a \"fields\" directory in the current directory. Use the --output-directory to generate the file in the directory that contains the custom metadata type metdata files, such as \"force-app/main/default/objects/MyCmdt__mdt\" for the custom metadata type called MyCmdt.",
10
11
  "examples": [
11
12
  "Generate a metadata file for a custom checkbox field and add the file to the MyCmdt__mdt/fields directory:\n<%= config.bin %> <%= command.id %> --name MyCheckboxField --type Checkbox --output-directory force-app/main/default/objects/MyCmdt__mdt",
@@ -182,6 +183,7 @@
182
183
  "force:cmdt:generate"
183
184
  ],
184
185
  "args": {},
186
+ "deprecateAliases": true,
185
187
  "description": "Use this command to migrate existing custom objects or custom settings in an org to custom metadata types. If a field of the Salesforce object is of an unsupported type, the field type is automatically converted to text. Run \"<%= config.bin %> cmdt generate field --help\" to see the list of supported cmdt field types, listed in the --type flag summary. Use the --ignore-unsupported to ignore these fields.\n\nThis command creates the metadata files that describe the new custom metadata type and its fields in the \"force-app/main/default/objects/TypeName__mdt\" directory by default, where \"TypeName\" is the value of the required --dev-name flag. Use --type-output-directory to create them in a different directory.",
186
188
  "examples": [
187
189
  "Generate a custom metadata type from a custom object called MySourceObject__c in your default org:\n<%= config.bin %> <%= command.id %> --dev-name MyCMDT --sobject MySourceObject__c",
@@ -371,6 +373,7 @@
371
373
  "cmdt:create"
372
374
  ],
373
375
  "args": {},
376
+ "deprecateAliases": true,
374
377
  "description": "This command creates a metadata file that describes the new custom metadata type. By default, the file is created in the MyCustomType__mdt directory in the current directory, where MyCustomType is the value of the required --type-name flag. Use the --output-directory to generate the file in a package directory with other custom metadata types, such as \"force-app/main/default/objects\".",
375
378
  "examples": [
376
379
  "Generate a custom metadata type with developer name 'MyCustomType'; this name is also used as the label:\n<%= config.bin %> <%= command.id %> --type-name MyCustomType",
@@ -500,6 +503,7 @@
500
503
  "cmdt:record:create"
501
504
  ],
502
505
  "args": {},
506
+ "deprecateAliases": true,
503
507
  "description": "The custom metadata type must already exist in your project. You must specify a name for the new record. Use name=value pairs to specify the values for the fields, such as MyTextField=\"some text here\" or MyNumberField=32.",
504
508
  "examples": [
505
509
  "Create a record metadata file for custom metadata type 'MyCMT' with specified values for two custom fields:\n<%= config.bin %> <%= command.id %> --type-name MyCMT__mdt --record-name MyRecord My_Custom_Field_1=Foo My_Custom_Field_2=Bar",
@@ -662,6 +666,7 @@
662
666
  "cmdt:record:insert"
663
667
  ],
664
668
  "args": {},
669
+ "deprecateAliases": true,
665
670
  "description": "The custom metadata type must already exist in your project. By default, the Name column is used to determine the record name; use the --name-column flag to specify a different column.",
666
671
  "examples": [
667
672
  "Generate record metadata files from values in a CSV file for the custom metadata type MyCmdt. Use 'Name' as the column that specifies the record name:\n<%= config.bin %> <%= command.id %> --csv path/to/my.csv --type-name MyCmdt",
@@ -5240,5 +5245,5 @@
5240
5245
  ]
5241
5246
  }
5242
5247
  },
5243
- "version": "2.23.19"
5248
+ "version": "2.24.0"
5244
5249
  }
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@salesforce/cli",
3
3
  "description": "The Salesforce CLI",
4
- "version": "2.23.19",
4
+ "version": "2.24.0",
5
5
  "author": "Salesforce",
6
6
  "bin": {
7
7
  "sf": "./bin/run.js",
@@ -71,7 +71,7 @@
71
71
  "@salesforce/plugin-user"
72
72
  ],
73
73
  "jitPlugins": {
74
- "@salesforce/plugin-custom-metadata": "3.0.12",
74
+ "@salesforce/plugin-custom-metadata": "3.1.1",
75
75
  "@salesforce/plugin-community": "3.0.10",
76
76
  "@salesforce/plugin-dev": "2.1.3",
77
77
  "@salesforce/plugin-devops-center": "1.2.5",
@@ -133,12 +133,12 @@
133
133
  }
134
134
  },
135
135
  "dependencies": {
136
- "@oclif/core": "3.15.1",
136
+ "@oclif/core": "3.16.0",
137
137
  "@oclif/plugin-autocomplete": "3.0.4",
138
- "@oclif/plugin-commands": "3.0.8",
138
+ "@oclif/plugin-commands": "3.1.0",
139
139
  "@oclif/plugin-help": "6.0.9",
140
140
  "@oclif/plugin-not-found": "3.0.7",
141
- "@oclif/plugin-plugins": "4.1.13",
141
+ "@oclif/plugin-plugins": "4.1.14",
142
142
  "@oclif/plugin-search": "1.0.10",
143
143
  "@oclif/plugin-update": "4.1.7",
144
144
  "@oclif/plugin-version": "2.0.11",
@@ -146,22 +146,22 @@
146
146
  "@oclif/plugin-which": "3.0.14",
147
147
  "@salesforce/core": "^6.1.4",
148
148
  "@salesforce/plugin-apex": "3.0.14",
149
- "@salesforce/plugin-auth": "3.0.15",
149
+ "@salesforce/plugin-auth": "3.1.0",
150
150
  "@salesforce/plugin-data": "3.0.13",
151
- "@salesforce/plugin-deploy-retrieve": "2.2.12",
151
+ "@salesforce/plugin-deploy-retrieve": "2.2.13",
152
152
  "@salesforce/plugin-info": "3.0.13",
153
- "@salesforce/plugin-limits": "3.0.11",
153
+ "@salesforce/plugin-limits": "3.1.0",
154
154
  "@salesforce/plugin-marketplace": "1.0.15",
155
- "@salesforce/plugin-org": "3.1.7",
156
- "@salesforce/plugin-packaging": "2.0.1",
157
- "@salesforce/plugin-schema": "3.0.10",
155
+ "@salesforce/plugin-org": "3.2.0",
156
+ "@salesforce/plugin-packaging": "2.0.2",
157
+ "@salesforce/plugin-schema": "3.1.0",
158
158
  "@salesforce/plugin-settings": "2.0.14",
159
159
  "@salesforce/plugin-sobject": "1.0.7",
160
- "@salesforce/plugin-source": "3.0.10",
160
+ "@salesforce/plugin-source": "3.1.0",
161
161
  "@salesforce/plugin-telemetry": "3.1.8",
162
162
  "@salesforce/plugin-templates": "56.0.8",
163
163
  "@salesforce/plugin-trust": "3.2.5",
164
- "@salesforce/plugin-user": "3.1.5",
164
+ "@salesforce/plugin-user": "3.2.0",
165
165
  "@salesforce/sf-plugins-core": "5.0.13",
166
166
  "debug": "^4.3.4"
167
167
  },