edf2csv 0.7.83 → 0.7.84

package/dist/cli.js

@@ -18,7 +18,7 @@ import process from 'node:process';
 import { EdfError } from './edf/errors.js';
 import { EdfFile } from './edf/reader.js';
 import { buildPlan, withoutFileRateWarning } from './convert/plan.js';
-import { ConversionError, USAGE_ERROR_CODES, auditStdout, convert, defaultOutputDir, durationDiagnostics, requestedAnnotationWindow, stdoutRefusal, } from './convert/run.js';
+import { ConversionError, USAGE_ERROR_CODES, auditStdout, convert, defaultOutputDir, durationDiagnostics, requestedAnnotationWindow, noSignalFile, stdoutRefusal, } from './convert/run.js';
 import { ChannelSelectionError } from './convert/channels.js';
 // Shared with the library so a bad option is the same error whichever way it arrived.
 import { OptionError } from './convert/options.js';
@@ -867,6 +867,19 @@ async function showInfo(input, shared, asJson, jsonIndent, batch = false, toStdo
             from: plan.range.startSeconds,
             to: plan.range.endSeconds,
         }));
+        /*
+          And the warning about the signal file this conversion would not write.
+    
+          `--info` prints one accurate line about it in the report body — "Would write
+          channels.csv and no signal data" — and raised nothing, so the one mode whose purpose is
+          to say what a conversion will do carried a shorter warning list than the conversion did.
+          `--info --strict` is documented as a cheap way to screen a directory before converting
+          it, and on a recording of nothing but annotations it reported one warning where the
+          conversion reports two.
+        */
+        const missing = noSignalFile(file, plan);
+        if (missing)
+            plan.diagnostics.push(missing);
         if (toStdout) {
             const refusal = stdoutRefusal(file, plan);
             if (refusal) {