@salesforce/plugin-templates 55.5.7 → 55.5.9

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.
Files changed (31) hide show
  1. package/lib/commands/apex/generate/class.js +1 -1
  2. package/lib/commands/apex/generate/class.js.map +1 -1
  3. package/lib/commands/apex/generate/trigger.js +4 -4
  4. package/lib/commands/apex/generate/trigger.js.map +1 -1
  5. package/lib/commands/lightning/generate/app.js +2 -2
  6. package/lib/commands/lightning/generate/app.js.map +1 -1
  7. package/lib/commands/lightning/generate/component.js +3 -3
  8. package/lib/commands/lightning/generate/component.js.map +1 -1
  9. package/lib/commands/lightning/generate/event.js +2 -2
  10. package/lib/commands/lightning/generate/event.js.map +1 -1
  11. package/lib/commands/lightning/generate/interface.js +2 -2
  12. package/lib/commands/lightning/generate/interface.js.map +1 -1
  13. package/lib/commands/lightning/generate/test.js +2 -2
  14. package/lib/commands/lightning/generate/test.js.map +1 -1
  15. package/lib/commands/project/generate.js +8 -8
  16. package/lib/commands/project/generate.js.map +1 -1
  17. package/lib/commands/visualforce/generate/component.js +3 -3
  18. package/lib/commands/visualforce/generate/component.js.map +1 -1
  19. package/lib/commands/visualforce/generate/page.js +3 -3
  20. package/lib/commands/visualforce/generate/page.js.map +1 -1
  21. package/lib/tsconfig.tsbuildinfo +1 -1
  22. package/lib/utils/flags.js +3 -3
  23. package/lib/utils/flags.js.map +1 -1
  24. package/messages/apexTrigger.md +5 -6
  25. package/messages/lightning.md +3 -3
  26. package/messages/lightningCmp.md +2 -2
  27. package/messages/messages.md +2 -2
  28. package/messages/project.md +8 -8
  29. package/messages/vf.md +2 -2
  30. package/oclif.manifest.json +3 -3
  31. package/package.json +18 -20
@@ -1,4 +1,4 @@
1
- # flags.outputdir
1
+ # flags.outputdir.summary
2
2
 
3
3
  Directory for saving the created files.
4
4
 
@@ -10,7 +10,7 @@ The location can be an absolute path or relative to the current working director
10
10
 
11
11
  If you don’t specify an outputdir, we create a subfolder in your current working directory with the name of your bundle. For example, if the current working directory is force-app and your Lightning bundle is called myBundle, we create force-app/myBundle/ to store the files in the bundle.
12
12
 
13
- # flags.template
13
+ # flags.template.summary
14
14
 
15
15
  Template to use for file creation.
16
16
 
@@ -26,7 +26,7 @@ By default, the generated sfdx-project.json file sets the sourceApiVersion prope
26
26
 
27
27
  <%= config.bin %> <%= command.id %> --name mywork --template empty
28
28
 
29
- # flags.name
29
+ # flags.name.summary
30
30
 
31
31
  Name of the generated project.
32
32
 
@@ -34,7 +34,7 @@ Name of the generated project.
34
34
 
35
35
  Generates a project directory with this name; any valid directory name is accepted. Also sets the "name" property in the sfdx-project.json file to this name.
36
36
 
37
- # flags.template
37
+ # flags.template.summary
38
38
 
39
39
  Template to use for project creation.
40
40
 
@@ -58,7 +58,7 @@ The standard template provides a complete force-app directory structure so you k
58
58
 
59
59
  The analytics template provides similar files and the force-app/main/default/waveTemplates directory.
60
60
 
61
- # flags.namespace
61
+ # flags.namespace.summary
62
62
 
63
63
  Namespace associated with this project and any connected scratch orgs.
64
64
 
@@ -66,15 +66,15 @@ Namespace associated with this project and any connected scratch orgs.
66
66
 
67
67
  Will set this version as sourceApiVersion in the sfdx-project.json file
68
68
 
69
- # flags.packagedir
69
+ # flags.default-package-dir.summary
70
70
 
71
71
  Default package directory name.
72
72
 
73
- # flags.packagedir.description
73
+ # flags.default-package-dir.description
74
74
 
75
75
  Metadata items such as classes and Lightning bundles are placed inside this folder.
76
76
 
77
- # flags.manifest
77
+ # flags.manifest.summary
78
78
 
79
79
  Generate a manifest (package.xml) for change-set based development.
80
80
 
@@ -82,10 +82,10 @@ Generate a manifest (package.xml) for change-set based development.
82
82
 
83
83
  Generates a default manifest (package.xml) for fetching Apex, Visualforce, Lightning components, and static resources.
84
84
 
85
- # flags.loginurl
85
+ # flags.login-url.summary
86
86
 
87
87
  Salesforce instance login URL.
88
88
 
89
- # flags.loginurl.description
89
+ # flags.login-url.description
90
90
 
91
91
  Normally defaults to https://login.salesforce.com.
package/messages/vf.md CHANGED
@@ -6,7 +6,7 @@ Generate a Visualforce %s.
6
6
 
7
7
  The command generates the .%s file and associated metadata file in the specified directory or the current working directory by default.
8
8
 
9
- # flags.name
9
+ # flags.name.summary
10
10
 
11
11
  Name of the generated Visualforce %s.
12
12
 
@@ -14,7 +14,7 @@ Name of the generated Visualforce %s.
14
14
 
15
15
  The name can be up to 40 characters and must start with a letter.
16
16
 
17
- # flags.label
17
+ # flags.label.summary
18
18
 
19
19
  Visualforce %s label.
20
20
 
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "55.5.7",
2
+ "version": "55.5.9",
3
3
  "commands": {
4
4
  "project:generate": {
5
5
  "id": "project:generate",
@@ -387,7 +387,7 @@
387
387
  "apex:generate:trigger": {
388
388
  "id": "apex:generate:trigger",
389
389
  "summary": "Generate an Apex trigger.",
390
- "description": "Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent directory called \"triggers\" in your package directory. Either run this command from an existing directory of this name, or use the --output-dir flag to generate one or point to an existing one. \n\nIf you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with the Salesforce object you want to generate a trigger for. If you don't specify --event, \"before insert\" is used.",
390
+ "description": "Generates the Apex trigger \\*.trigger file and associated metadata file. These files must be contained in a parent directory called \"triggers\" in your package directory. Either run this command from an existing directory of this name, or use the --output-dir flag to generate one or point to an existing one.\n\nIf you don't specify the --sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with the Salesforce object you want to generate a trigger for. If you don't specify --event, \"before insert\" is used.",
391
391
  "strict": true,
392
392
  "pluginName": "@salesforce/plugin-templates",
393
393
  "pluginAlias": "@salesforce/plugin-templates",
@@ -604,7 +604,7 @@
604
604
  "lightning:generate:component": {
605
605
  "id": "lightning:generate:component",
606
606
  "summary": "Generate a bundle for an Aura component or a Lightning web component.",
607
- "description": "Generates the bundle in the specified directory or the current working directory. The bundle consists of multiple files in a directory with the designated name. Lightning web components are contained in the directory with name \"lwc\", Aura components in \"aura\".\n\nTo generate a Lightning web component, pass \"--type lwc\" to the command. If you don’t specify --type, Salesforce CLI generates an Aura component by default.",
607
+ "description": "Generates the bundle in the specified directory or the current working directory. The bundle consists of multiple files in a directory with the designated name. Lightning web components are contained in the directory with name \"lwc\", Aura components in \"aura\".\n\nTo generate a Lightning web component, pass \"--type lwc\" to the command. If you don’t specify --type, Salesforce CLI generates an Aura component by default.",
608
608
  "strict": true,
609
609
  "pluginName": "@salesforce/plugin-templates",
610
610
  "pluginAlias": "@salesforce/plugin-templates",
package/package.json CHANGED
@@ -1,56 +1,55 @@
1
1
  {
2
2
  "name": "@salesforce/plugin-templates",
3
3
  "description": "Commands to create metadata from a default or custom template",
4
- "version": "55.5.7",
4
+ "version": "55.5.9",
5
5
  "main": "lib/index.js",
6
6
  "author": "Salesforce",
7
7
  "bugs": "https://github.com/salesforcecli/plugin-templates/issues",
8
8
  "dependencies": {
9
- "@oclif/core": "^2.9.4",
10
- "@salesforce/core": "^4.2.1",
11
- "@salesforce/sf-plugins-core": "^3.1.4",
12
- "@salesforce/templates": "^57.1.2",
9
+ "@oclif/core": "^2.11.8",
10
+ "@salesforce/core": "^5.2.0",
11
+ "@salesforce/sf-plugins-core": "^3.1.14",
12
+ "@salesforce/templates": "^59.0.1",
13
13
  "tslib": "^2",
14
14
  "yeoman-environment": "^3.19.3",
15
15
  "yeoman-generator": "^5.9.0"
16
16
  },
17
17
  "devDependencies": {
18
- "@oclif/plugin-command-snapshot": "^4.0.5",
19
- "@oclif/plugin-help": "^5.2.11",
20
- "@salesforce/cli-plugins-testkit": "^4.2.6",
18
+ "@oclif/plugin-command-snapshot": "^4.0.11",
19
+ "@salesforce/cli-plugins-testkit": "^4.2.9",
21
20
  "@salesforce/dev-config": "^4.0.1",
22
- "@salesforce/dev-scripts": "^5.4.3",
23
- "@salesforce/plugin-command-reference": "^3.0.10",
24
- "@salesforce/plugin-settings": "^1.4.15",
21
+ "@salesforce/dev-scripts": "^5.7.0",
22
+ "@salesforce/plugin-command-reference": "^3.0.25",
23
+ "@salesforce/plugin-settings": "^1.4.24",
25
24
  "@salesforce/prettier-config": "^0.0.3",
26
25
  "@salesforce/ts-sinon": "^1.4.11",
27
- "@swc/core": "^1.3.69",
26
+ "@swc/core": "^1.3.74",
28
27
  "@types/yeoman-assert": "^3.1.1",
29
28
  "@types/yeoman-environment": "^2.10.8",
30
29
  "@types/yeoman-generator": "^5.2.11",
31
30
  "@typescript-eslint/eslint-plugin": "^5.60.1",
32
31
  "@typescript-eslint/parser": "^5.61.0",
33
32
  "chai": "^4.3.7",
34
- "eslint": "^8.44.0",
33
+ "eslint": "^8.45.0",
35
34
  "eslint-config-prettier": "^8.8.0",
36
- "eslint-config-salesforce": "^2.0.1",
35
+ "eslint-config-salesforce": "^2.0.2",
37
36
  "eslint-config-salesforce-license": "^0.2.0",
38
37
  "eslint-config-salesforce-typescript": "^1.1.1",
39
38
  "eslint-plugin-header": "^3.1.1",
40
39
  "eslint-plugin-import": "2.27.5",
41
40
  "eslint-plugin-jsdoc": "^43.0.5",
42
- "eslint-plugin-sf-plugin": "^1.15.13",
41
+ "eslint-plugin-sf-plugin": "^1.16.1",
43
42
  "husky": "^7.0.4",
44
43
  "mocha": "^9.1.3",
45
44
  "nyc": "^15.1.0",
46
- "oclif": "^3.9.1",
45
+ "oclif": "^3.10.0",
47
46
  "prettier": "^2.8.8",
48
47
  "pretty-quick": "^3.1.0",
49
48
  "shx": "^0.3.4",
50
49
  "sinon": "10.0.0",
51
50
  "ts-node": "^10.0.0",
52
51
  "typescript": "^4.9.5",
53
- "wireit": "^0.9.5",
52
+ "wireit": "^0.10.0",
54
53
  "yeoman-assert": "^3.1.1",
55
54
  "yeoman-test": "^6.3.0"
56
55
  },
@@ -81,7 +80,6 @@
81
80
  ],
82
81
  "bin": "sfdx",
83
82
  "devPlugins": [
84
- "@oclif/plugin-help",
85
83
  "@oclif/plugin-command-snapshot",
86
84
  "@salesforce/plugin-command-reference",
87
85
  "@salesforce/plugin-settings"
@@ -270,7 +268,7 @@
270
268
  }
271
269
  },
272
270
  "sfdx": {
273
- "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-templates/55.5.7.crt",
274
- "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-templates/55.5.7.sig"
271
+ "publicKeyUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-templates/55.5.9.crt",
272
+ "signatureUrl": "https://developer.salesforce.com/media/salesforce-cli/security/@salesforce/plugin-templates/55.5.9.sig"
275
273
  }
276
274
  }