@shibanet0/datamitsu-config 0.4.1 → 0.5.0

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 (12) hide show
  1. package/datamitsu.config.base.js +1423 -879
  2. package/datamitsu.config.js +1423 -879
  3. package/datamitsu.config.oci-dockerhub.js +1424 -880
  4. package/datamitsu.config.oci-ghcr.js +1424 -880
  5. package/dist/apps/knip/index.d.ts +4 -6
  6. package/dist/datamitsu-config/inline-config/eslint.d.ts +1 -1
  7. package/dist/datamitsu-config/inline-config/knip.d.ts +1 -1
  8. package/dist/datamitsu-config/inline-config/lefthook-proxy.d.ts +1 -1
  9. package/dist/datamitsu-config/inline-config/sort-keys.d.ts +1 -1
  10. package/dist/datamitsu-config/parsers.d.ts +1 -1
  11. package/package.json +2 -2
  12. package/dist/datamitsu-config/managed-configs/_datamitsu_scripts_check_empty_files_sh.d.ts +0 -1
package/dist/apps/knip/index.d.ts CHANGED
@@ -41,12 +41,10 @@ export type DefineConfigOptions = {
41
41
  /**
42
42
  * Severities this config emits, and the only ones it accepts.
43
43
  *
44
- * Knip's own `warn` is deliberately absent. It is a real tier there — a `warn` finding is reported
45
- * and excluded from the count that sets the exit code — but datamitsu reads knip through
46
- * `--reporter json`, and that reporter carries no severity at all. A warned finding arrives
47
- * indistinguishable from an errored one, the parser renders every finding as an error, and the run
48
- * still exits zero: red diagnostics on a green tool. Better that the tier cannot be written at all
49
- * than that it mean that.
44
+ * Knip's JSON reporter carries no severity. Datamitsu therefore resolves every finding from a
45
+ * passing process to warning and every finding from a failing process to error. In a mixed run,
46
+ * Knip's nonzero exit makes its warning-tier findings indistinguishable from errors. Better that
47
+ * the tier cannot be written at all than that its meaning depends on what else the same run found.
50
48
  */
51
49
  export type IssueSeverity = "error" | "off";
52
50
  /**