@ingenioz-it/caits 0.6.0 → 0.8.0

package/template/project/AGENTS

@@ -13,7 +13,7 @@ A CAITS project (Clean Architecture In TypeScript): a Marko app with a backend a
 
 - The business lives in bounded contexts: `src/backend/<context>/` and `src/frontend/<context>/`, each with `domain/`, `infra/`, its use cases in `command/` and `query/`, and a `di.ts`. A frontend context has `event/` and `presentation/` too. To add one, copy the shape of an existing one.
 - Domain: entities, value objects, errors, domain events, and ports (`domain/port/<port>/`), each with its contract (`<Port>.contract.ts`).
-- Use cases: one folder per use case, `command/<use-case>/` or `query/<use-case>/`, which holds all of it: its DTOs, its handler and its test, `<use-case>.application.test.ts`, and in the backend its controllers, `<use-case>.<name>.controller.ts` (`<use-case>.http.controller.ts` for HTTP), each with its test, `<use-case>.<name>.presentation.test.ts`. An endpoint lives in one folder, and the name of a test says the layer that it tests. A use case imports nothing from another use case: what they share lives in the domain.
+- Use cases: one folder per use case, `command/<use-case>/` or `query/<use-case>/`, which holds all of it: its DTOs (plain classes), its handler and its test, `<use-case>.application.test.ts`, and in the backend its controllers, `<use-case>.<name>.controller.ts` (`<use-case>.http.controller.ts` for HTTP), each with its test, `<use-case>.<name>.presentation.test.ts`. An endpoint lives in one folder, and the name of a test says the layer that it tests. A use case imports nothing from another use case: what they share lives in the domain. The `execute` of a handler takes the input DTO, typed with its class: CAITS finds the use case by this type.
 - Infra: the adapters of the ports, in `infra/<port>/`. The test of each adapter runs the contract of its port.
 - Frontend: its events, one file each in `event/`, and its presentation, which serves several use cases: the views (`presentation/view/<view>/`), which the routes place; the components, `presentation/component/<component>/`, the parts that the views place; and the store (`presentation/store/`), if the context has use cases. A view and a component take the frontend of their context only, publish its events and read its store. A view imports no other view, and a component no view.
 - The contexts talk through the context shared, `src/backend/shared/` and `src/frontend/shared/`, and their context map, `context-map.ts` beside their di.ts. A handler (in the frontend, also a view or a component) publishes an event of its context; the context map, `share(Event, event => [...])`, turns it into events of shared on the shared bus (the event of the context holds what they need). The context map of each context that hears it, `when(Event, event => [...])`, turns it into input DTOs of the context (backend) or into events of the context (frontend). Each line goes one way, reads only its event, and the lines make no cycle. A context names only itself and shared, never another context: only its context map imports the events of shared.

package/quality/mutation-suite.mjs

@@ -1,82 +0,0 @@
-// `caits mutation-suite`: the command that Stryker runs for each mutant. It runs the unit tests from a private copy of the sandbox.
-// Stryker runs many suites at once in a single sandbox, and every Vitest start rewrites the files that the Marko plugin generates
-// (dist/, .marko-run/): suites that run at the same time would fail at random, and a failed run counts as a killed mutant.
-// The copy shares the packages of the sandbox, not the caches that the tools keep beside them (node_modules/.vite/, .vitest-cache/…): the
-// cache of Vite depends on the folder of the project, so each suite would write it again while the others read it.
-import { spawn } from "node:child_process";
-import { cpSync, existsSync, mkdirSync, mkdtempSync, readdirSync, rmSync, symlinkSync } from "node:fs";
-import { constants, tmpdir } from "node:os";
-import { join } from "node:path";
-import { painterOf } from "./terminal.mjs";
-
-const ENTRIES = ["src", "test", "quality", "dist", ".marko-run", "package.json", "tsconfig.json"];
-
-/** The report of Vitest, in the copy: Vitest writes it once the tests ran, also when one fails. */
-const REPORT = "vitest-report.json";
-
-/**
- * What the suite prints when the unit tests did not run. Stryker counts the mutant as killed, as for any exit code but 0:
- * `caits mutation-summary` finds these words in the report of Stryker, and does not.
- */
-export const NOT_RUN = "The unit tests did not run";
-
-/** The copies, in the temporary folder: `caits-mutation-<pid of their suite>-<random>`. */
-const COPY = /^caits-mutation-(\d+)-/;
-
-/** @param {string[]} args the options of Vitest, which Stryker gives */
-export async function run(args) {
-  removeOrphans();
-  const sandbox = process.cwd();
-  const copy = mkdtempSync(join(tmpdir(), `caits-mutation-${process.pid}-`));
-  const remove = () => rmSync(copy, { recursive: true, force: true });
-  for (const entry of ENTRIES) {
-    if (existsSync(join(sandbox, entry))) cpSync(join(sandbox, entry), join(copy, entry), { recursive: true });
-  }
-  // The packages and their commands (.bin/). The other entries that start with a dot are the caches and the files of the tools.
-  mkdirSync(join(copy, "node_modules"));
-  for (const entry of readdirSync(join(sandbox, "node_modules"))) {
-    if (!entry.startsWith(".") || entry === ".bin") symlinkSync(join(sandbox, "node_modules", entry), join(copy, "node_modules", entry));
-  }
-
-  // The suite builds in the dist/ of its copy: the build folder that `caits check` gives (CAITS_OUT_DIR) is in node_modules/, which the
-  // suites share.
-  const { CAITS_OUT_DIR: _, ...env } = process.env;
-  const vitest = ["vitest", "run", "--config", "quality/vite.config.ts", "--reporter=dot", "--reporter=json", `--outputFile.json=${REPORT}`, ...args];
-  const suite = spawn("npx", vitest, { cwd: copy, env, stdio: "inherit" });
-  // Ctrl+C and `caits check` stop the suite: the copy goes away with it. The exit code tells the signal: 130 for SIGINT, 143 for SIGTERM.
-  for (const signal of /** @type {const} */ (["SIGINT", "SIGTERM"])) process.on(signal, () => { suite.kill(signal); remove(); process.exit(128 + constants.signals[signal]); });
-  /** @type {number} */
-  const status = await new Promise(resolve => suite.on("close", code => resolve(code ?? 1)));
-  const ran = existsSync(join(copy, REPORT));
-  remove();
-  // Vitest stopped before the tests, on an error of its own or of the system: no test failed, and the mutant is not tested.
-  if (status !== 0 && !ran) console.error(painterOf(process.stderr)("red", `${NOT_RUN}: Vitest stopped before them (exit ${status}). The mutant is not tested.`));
-  return status;
-}
-
-/**
- * Stryker stops a suite that takes too long with SIGKILL, which no code can follow: its copy stays. Each suite removes the copies whose
- * suite no longer runs.
- */
-function removeOrphans() {
-  for (const entry of readdirSync(tmpdir())) {
-    const pid = COPY.exec(entry)?.[1];
-    if (pid === undefined || runs(Number(pid))) continue;
-    try {
-      rmSync(join(tmpdir(), entry), { recursive: true, force: true });
-    } catch {
-      // The copy of another user.
-    }
-  }
-}
-
-/** @param {number} pid */
-function runs(pid) {
-  try {
-    process.kill(pid, 0);
-    return true;
-  } catch (error) {
-    // EPERM: the process runs, but belongs to another user.
-    return /** @type {NodeJS.ErrnoException} */ (error).code === "EPERM";
-  }
-}

package/src/messaging/Input.ts

@@ -1,4 +0,0 @@
-/** An input DTO of a context, a command or a query. `Output` is the DTO its handler answers with. */
-export abstract class Input<Output> {
-  declare protected readonly output?: Output;
-}