@salesforce/sf-plugins-core 2.0.0-beta.7 → 2.0.0-beta.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.
@@ -86,16 +86,17 @@ exports.optionalHubFlagWithDeprecations = (0, orgFlags_1.optionalHubFlag)({
86
86
  exports.arrayWithDeprecation = core_1.Flags.custom({
87
87
  multiple: true,
88
88
  delimiter: ',',
89
+ // eslint-disable-next-line @typescript-eslint/ban-ts-comment
90
+ // @ts-expect-error parse expects to return string[] but we need to return string.
91
+ // This is a weird consequence of implementing an array flag. The oclif parser splits the input (e.g. "thing1,thing2")
92
+ // on the delimiter and passes each value individually to the parse function. However, the return type needs to be
93
+ // string[] so that upstream consumers have the correct flag typings.
89
94
  parse: async (input, ctx) => {
90
95
  const inputParts = ctx.token.input.split(',').map((i) => i.trim());
91
96
  if (inputParts.length > 1) {
92
97
  await core_2.Lifecycle.getInstance().emitWarning(messages.getMessage('warning.arrayInputFormat'));
93
98
  }
94
- // This is a weird consequence of implementing an array flag. The oclif parser splits the input (e.g. "thing1,thing2")
95
- // on the delimiter and passes each value individually to the parse function. However, the return type needs to be
96
- // string[] so that upstream consumers have the correct flag typings. So we simply wrap the individual elements in
97
- // an array to satisfy typescript. Oclif ensures that the user ends up with a flat array of parsed strings.
98
- return [input];
99
+ return input;
99
100
  },
100
101
  });
101
102
  //# sourceMappingURL=compatibility.js.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@salesforce/sf-plugins-core",
3
- "version": "2.0.0-beta.7",
3
+ "version": "2.0.0-beta.9",
4
4
  "description": "Utils for writing Salesforce CLI plugins",
5
5
  "main": "lib/exported",
6
6
  "types": "lib/exported.d.ts",
@@ -33,7 +33,7 @@
33
33
  ],
34
34
  "dependencies": {
35
35
  "@oclif/core": "^2.0.7",
36
- "@salesforce/core": "^3.32.12",
36
+ "@salesforce/core": "^3.33.1",
37
37
  "@salesforce/kit": "^1.8.3",
38
38
  "@salesforce/ts-types": "^1.7.1",
39
39
  "chalk": "^4",
@@ -52,11 +52,11 @@
52
52
  "eslint": "^8.32.0",
53
53
  "eslint-config-prettier": "^8.6.0",
54
54
  "eslint-config-salesforce": "^1.1.0",
55
- "eslint-config-salesforce-license": "^0.1.6",
55
+ "eslint-config-salesforce-license": "^0.2.0",
56
56
  "eslint-config-salesforce-typescript": "^1.1.1",
57
57
  "eslint-plugin-header": "^3.1.1",
58
58
  "eslint-plugin-import": "^2.27.5",
59
- "eslint-plugin-jsdoc": "^39.6.4",
59
+ "eslint-plugin-jsdoc": "^39.7.0",
60
60
  "husky": "^7.0.4",
61
61
  "mocha": "^9.1.3",
62
62
  "nyc": "^15.1.0",