@webpieces/code-rules 0.4.620 → 0.4.622

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webpieces/code-rules",
-  "version": "0.4.620",
+  "version": "0.4.622",
   "description": "Standalone code validation rules extracted from architecture-validators, no Nx dependency required",
   "type": "commonjs",
   "main": "./src/index.js",
@@ -16,7 +16,7 @@
     "directory": "packages/tooling/code-rules"
   },
   "dependencies": {
-    "@webpieces/rules-config": "0.4.620",
+    "@webpieces/rules-config": "0.4.622",
     "@inversifyjs/binding-decorators": "1.1.5",
     "inversify": "7.10.4",
     "reflect-metadata": "0.2.2"
@@ -27,6 +27,7 @@
   "types": "./src/index.d.ts",
   "bin": {
     "wp-validate-code": "./src/cli.js",
-    "wp-ci": "./src/wp-ci.js"
+    "wp-ci": "./src/wp-ci.js",
+    "wp-prune-unknown-config": "./src/prune-unknown-config.js"
   }
 }

package/src/prune-unknown-config.d.ts

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import 'reflect-metadata';

package/src/prune-unknown-config.js

@@ -0,0 +1,28 @@
+#!/usr/bin/env node
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+require("reflect-metadata");
+const inversify_1 = require("inversify");
+const rules_config_1 = require("@webpieces/rules-config");
+/**
+ * `wp-prune-unknown-config` — strip every key from webpieces.config.json that no running validator has a
+ * schema for, and say which ones went.
+ *
+ * This is the command the unknown-rule error and the validation banner both name. It exists because the
+ * moment that advice is read is the worst moment to act on it by hand: the hook guard denies every Bash
+ * call while the config is invalid, so the reader is editing JSON blind. One command makes cleanliness
+ * the default path instead of a judgement call taken under a total block.
+ *
+ * It lives in code-rules rather than rules-config because rules-config is a library with no bins, and
+ * code-rules already ships `wp-validate-code` — the command whose failure sends a reader here. All the
+ * logic is `ConfigPruner`; this file is the composition root and nothing else.
+ */
+(0, rules_config_1.runMain)(async () => {
+    const container = new inversify_1.Container({ autobind: true });
+    // Reject `--help`/bogus flags BEFORE anything rewrites a file — an ignored flag must never mutate config.
+    container.get(rules_config_1.CliArgs).assertNoArgs(new rules_config_1.CliUsage('wp-prune-unknown-config', 'Delete every rules/hookGuards key webpieces.config.json carries that no validator has a schema ' +
+        'for, naming each one. Leaves renames and in-file moves alone, and does nothing when rulesDir is set.'));
+    const result = container.get(rules_config_1.ConfigPruner).pruneFrom(process.cwd());
+    process.stdout.write(result.describeSelf() + '\n');
+});
+//# sourceMappingURL=prune-unknown-config.js.map

package/src/prune-unknown-config.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"prune-unknown-config.js","sourceRoot":"","sources":["../../../../../packages/tooling/code-rules/src/prune-unknown-config.ts"],"names":[],"mappings":";;;AACA,4BAA0B;AAC1B,yCAAsC;AACtC,0DAAgG;AAEhG;;;;;;;;;;;;GAYG;AACH,IAAA,sBAAO,EAAC,KAAK,IAAmB,EAAE;IAC9B,MAAM,SAAS,GAAG,IAAI,qBAAS,CAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,CAAC;IACpD,0GAA0G;IAC1G,SAAS,CAAC,GAAG,CAAC,sBAAO,CAAC,CAAC,YAAY,CAAC,IAAI,uBAAQ,CAC5C,yBAAyB,EACzB,iGAAiG;QACjG,sGAAsG,CAAC,CAAC,CAAC;IAC7G,MAAM,MAAM,GAAgB,SAAS,CAAC,GAAG,CAAC,2BAAY,CAAC,CAAC,SAAS,CAAC,OAAO,CAAC,GAAG,EAAE,CAAC,CAAC;IACjF,OAAO,CAAC,MAAM,CAAC,KAAK,CAAC,MAAM,CAAC,YAAY,EAAE,GAAG,IAAI,CAAC,CAAC;AACvD,CAAC,CAAC,CAAC","sourcesContent":["#!/usr/bin/env node\nimport 'reflect-metadata';\nimport { Container } from 'inversify';\nimport { runMain, CliArgs, CliUsage, ConfigPruner, PruneResult } from '@webpieces/rules-config';\n\n/**\n * `wp-prune-unknown-config` — strip every key from webpieces.config.json that no running validator has a\n * schema for, and say which ones went.\n *\n * This is the command the unknown-rule error and the validation banner both name. It exists because the\n * moment that advice is read is the worst moment to act on it by hand: the hook guard denies every Bash\n * call while the config is invalid, so the reader is editing JSON blind. One command makes cleanliness\n * the default path instead of a judgement call taken under a total block.\n *\n * It lives in code-rules rather than rules-config because rules-config is a library with no bins, and\n * code-rules already ships `wp-validate-code` — the command whose failure sends a reader here. All the\n * logic is `ConfigPruner`; this file is the composition root and nothing else.\n */\nrunMain(async (): Promise<void> => {\n    const container = new Container({ autobind: true });\n    // Reject `--help`/bogus flags BEFORE anything rewrites a file — an ignored flag must never mutate config.\n    container.get(CliArgs).assertNoArgs(new CliUsage(\n        'wp-prune-unknown-config',\n        'Delete every rules/hookGuards key webpieces.config.json carries that no validator has a schema ' +\n        'for, naming each one. Leaves renames and in-file moves alone, and does nothing when rulesDir is set.'));\n    const result: PruneResult = container.get(ConfigPruner).pruneFrom(process.cwd());\n    process.stdout.write(result.describeSelf() + '\\n');\n});\n"]}