@salesforce/plugin-metadata-enrichment 0.1.0 → 0.1.2
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.
- package/README.md +1 -3
- package/lib/commands/metadata/enrich.js +1 -1
- package/lib/commands/metadata/enrich.js.map +1 -1
- package/messages/errors.md +0 -4
- package/messages/metadata.enrich.md +0 -2
- package/npm-shrinkwrap.json +257 -286
- package/oclif.lock +1237 -1239
- package/oclif.manifest.json +2 -2
- package/package.json +6 -6
package/oclif.manifest.json
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
"metadata:enrich": {
|
|
4
4
|
"aliases": [],
|
|
5
5
|
"args": {},
|
|
6
|
-
"description": "Use this command to add AI-generated descriptions right in the metadata source files in your local DX project. These enriched descriptions succinctly outline the metadata component’s purpose and capabilities, which in turn provide context when vibe coding with an AI tool, such as Agentforce Vibes.\n\nThis command updates only the local metadata source files in your DX project; it doesn't change the components in your org. If you want the AI-generated descriptions in your org, then you must explicitly deploy the updated metadata components to your org by using, for example, the \"project deploy start\" CLI command.\n\nTo enrich multiple metadata components, specify multiple --metadata <name> flags. Enclose names that contain spaces in double quotes.\n\nEven though this command updates only local files in your DX project, you're still required to authorize and specify an org, which is how the command accesses a large language model (LLM).\n\nThis command currently supports the following metadata types:\n\n- LightningComponentBundle\n-
|
|
6
|
+
"description": "Use this command to add AI-generated descriptions right in the metadata source files in your local DX project. These enriched descriptions succinctly outline the metadata component’s purpose and capabilities, which in turn provide context when vibe coding with an AI tool, such as Agentforce Vibes.\n\nThis command updates only the local metadata source files in your DX project; it doesn't change the components in your org. If you want the AI-generated descriptions in your org, then you must explicitly deploy the updated metadata components to your org by using, for example, the \"project deploy start\" CLI command.\n\nTo enrich multiple metadata components, specify multiple --metadata <name> flags. Enclose names that contain spaces in double quotes.\n\nEven though this command updates only local files in your DX project, you're still required to authorize and specify an org, which is how the command accesses a large language model (LLM).\n\nThis command currently supports the following metadata types:\n\n- LightningComponentBundle\n- CustomObject\n\nYour org must be eligible for metadata enrichment. Your Salesforce admin can help with that.",
|
|
7
7
|
"examples": [
|
|
8
8
|
"Enrich the \"HelloWorld\" LightningComponentBundle metadata component in the local DX project; use your default org:\n<%= config.bin %> <%= command.id %> --metadata LightningComponentBundle:HelloWorld",
|
|
9
9
|
"Enrich the \"HelloWorld\" LightningComponentBundle metadata component and use the org with alias \"my-org\":\n<%= config.bin %> <%= command.id %> --metadata LightningComponentBundle:HelloWorld --target-org my-org",
|
|
@@ -72,5 +72,5 @@
|
|
|
72
72
|
]
|
|
73
73
|
}
|
|
74
74
|
},
|
|
75
|
-
"version": "0.1.
|
|
75
|
+
"version": "0.1.2"
|
|
76
76
|
}
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@salesforce/plugin-metadata-enrichment",
|
|
3
3
|
"description": "A Salesforce CLI plugin to enrich metadata for Salesforce resources",
|
|
4
|
-
"version": "0.1.
|
|
4
|
+
"version": "0.1.2",
|
|
5
5
|
"author": "Salesforce",
|
|
6
6
|
"bugs": "https://github.com/forcedotcom/cli/issues",
|
|
7
7
|
"dependencies": {
|
|
@@ -10,13 +10,13 @@
|
|
|
10
10
|
"@oclif/table": "^0.5.1",
|
|
11
11
|
"@salesforce/core": "^8.24.3",
|
|
12
12
|
"@salesforce/kit": "^3.2.4",
|
|
13
|
-
"@salesforce/metadata-enrichment": "^0.0.
|
|
13
|
+
"@salesforce/metadata-enrichment": "^0.0.17",
|
|
14
14
|
"@salesforce/sf-plugins-core": "^12",
|
|
15
|
-
"@salesforce/source-deploy-retrieve": "^12.
|
|
15
|
+
"@salesforce/source-deploy-retrieve": "^12.35.0"
|
|
16
16
|
},
|
|
17
17
|
"devDependencies": {
|
|
18
18
|
"@oclif/plugin-command-snapshot": "^5.3.8",
|
|
19
|
-
"@salesforce/cli-plugins-testkit": "^5.3.
|
|
19
|
+
"@salesforce/cli-plugins-testkit": "^5.3.57",
|
|
20
20
|
"@salesforce/dev-scripts": "^11.0.4",
|
|
21
21
|
"@salesforce/plugin-command-reference": "^3.1.79",
|
|
22
22
|
"@salesforce/source-testkit": "^2.2.172",
|
|
@@ -207,7 +207,7 @@
|
|
|
207
207
|
"type": "module",
|
|
208
208
|
"packageManager": "yarn@1.22.22",
|
|
209
209
|
"sfdx": {
|
|
210
|
-
"publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-metadata-enrichment/0.1.
|
|
211
|
-
"signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-metadata-enrichment/0.1.
|
|
210
|
+
"publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-metadata-enrichment/0.1.2.crt",
|
|
211
|
+
"signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-metadata-enrichment/0.1.2.sig"
|
|
212
212
|
}
|
|
213
213
|
}
|