@salesforce/plugin-metadata-enrichment 0.0.9 → 0.1.0

package/README.md

@@ -99,8 +99,12 @@ DESCRIPTION
   Even 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).
 
-  Currently, this command supports enriching only Lightning Web Components, represented by the LightningComponentBundle
-  metadata type.
+  This command currently supports the following metadata types:
+
+  - LightningComponentBundle
+  - FlexiPage
+  - CustomObject
+  - LightningTypeBundle
 
   Your org must be eligible for metadata enrichment. Your Salesforce admin can help with that.
 
@@ -122,12 +126,16 @@ EXAMPLES
 
     $ sf metadata enrich --metadata "LightningComponentBundle:Component\*"
 
+  Enrich metadata for a LightningComponentBundle and CustomObject:
+
+    $ sf metadata enrich --metadata LightningComponentBundle:Component1 --metadata CustomObject:Component2
+
 FLAG DESCRIPTIONS
   -m, --metadata=<value>...  Metadata type and optional component name to enrich.
 
     Wildcards ("_") are supported as long as you use double quotes, such as "LightningComponentBundle:MyClass_".
 ```
 
-_See code: [src/commands/metadata/enrich.ts](https://github.com/salesforcecli/plugin-metadata-enrichment/blob/0.0.9/src/commands/metadata/enrich.ts)_
+_See code: [src/commands/metadata/enrich.ts](https://github.com/salesforcecli/plugin-metadata-enrichment/blob/0.1.0/src/commands/metadata/enrich.ts)_
 
 <!-- commandsstop -->

package/messages/metadata.enrich.md

@@ -12,7 +12,12 @@ To enrich multiple metadata components, specify multiple --metadata <name> flags
 
 Even 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).
 
-Currently, this command supports enriching only Lightning Web Components, represented by the LightningComponentBundle metadata type.
+This command currently supports the following metadata types:
+
+- LightningComponentBundle
+- FlexiPage
+- CustomObject
+- LightningTypeBundle
 
 Your org must be eligible for metadata enrichment. Your Salesforce admin can help with that.
 
@@ -34,6 +39,10 @@ Your org must be eligible for metadata enrichment. Your Salesforce admin can hel
 
   <%= config.bin %> <%= command.id %> --metadata "LightningComponentBundle:Component\*"
 
+- Enrich metadata for a LightningComponentBundle and CustomObject:
+
+  <%= config.bin %> <%= command.id %> --metadata LightningComponentBundle:Component1 --metadata CustomObject:Component2
+
 # flags.metadata.summary
 
 Metadata type and optional component name to enrich.

package/npm-shrinkwrap.json

@@ -1,12 +1,12 @@
 {
   "name": "@salesforce/plugin-metadata-enrichment",
-  "version": "0.0.9",
+  "version": "0.1.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@salesforce/plugin-metadata-enrichment",
-      "version": "0.0.9",
+      "version": "0.1.0",
       "license": "Apache-2.0",
       "dependencies": {
         "@oclif/core": "^4",

package/oclif.manifest.json

@@ -3,12 +3,13 @@
     "metadata:enrich": {
       "aliases": [],
       "args": {},
-      "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\nCurrently, this command supports enriching only Lightning Web Components, represented by the LightningComponentBundle metadata type.\n\nYour org must be eligible for metadata enrichment. Your Salesforce admin can help with that.",
+      "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- FlexiPage\n- CustomObject\n- LightningTypeBundle\n\nYour org must be eligible for metadata enrichment. Your Salesforce admin can help with that.",
       "examples": [
         "Enrich the \"HelloWorld\" LightningComponentBundle metadata component in the local DX project; use your default org:\n<%= config.bin %> <%= command.id %> --metadata LightningComponentBundle:HelloWorld",
         "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",
         "Enrich metadata for multiple LightningComponentBundles using your default org:\n<%= config.bin %> <%= command.id %> --metadata LightningComponentBundle:Component1 --metadata LightningComponentBundle:Component2",
-        "Enrich metadata for multiple LightningComponentBundles using a matching wildcard:\n<%= config.bin %> <%= command.id %> --metadata \"LightningComponentBundle:Component\\*\""
+        "Enrich metadata for multiple LightningComponentBundles using a matching wildcard:\n<%= config.bin %> <%= command.id %> --metadata \"LightningComponentBundle:Component\\*\"",
+        "Enrich metadata for a LightningComponentBundle and CustomObject:\n<%= config.bin %> <%= command.id %> --metadata LightningComponentBundle:Component1 --metadata CustomObject:Component2"
       ],
       "flags": {
         "json": {
@@ -71,5 +72,5 @@
       ]
     }
   },
-  "version": "0.0.9"
+  "version": "0.1.0"
 }

package/package.json

@@ -1,7 +1,7 @@
 {
     "name": "@salesforce/plugin-metadata-enrichment",
     "description": "A Salesforce CLI plugin to enrich metadata for Salesforce resources",
-    "version": "0.0.9",
+    "version": "0.1.0",
     "author": "Salesforce",
     "bugs": "https://github.com/forcedotcom/cli/issues",
     "dependencies": {
@@ -207,7 +207,7 @@
     "type": "module",
     "packageManager": "yarn@1.22.22",
     "sfdx": {
-        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-metadata-enrichment/0.0.9.crt",
-        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-metadata-enrichment/0.0.9.sig"
+        "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-metadata-enrichment/0.1.0.crt",
+        "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-metadata-enrichment/0.1.0.sig"
     }
 }