IF Commons GitHub

changes/plugin

The changes check as a rule plugin of Mizan (commons 0020-ifccm FR-032), for what a folder of specifications can judge offline: the shape of a harness's declaration (a regulated domain claimed with no production day). The rules that read commits need a range and are the command's (changes.ts).

A plugin runs once for each specification, and a declaration is one for the harness, so the plugin reports it only for the specification it is anchored to (the first of the folder), and holdHarness anchors it. A finding of it is in the gate phase: a declaration that is wrong by itself is refused whatever the baseline holds.

import { declarationPlugin } from "./plugin.ts";
declarationPlugin({ regulatedDomains: ["DeviceQuality"] }, "ifccm.declaration.ts", "0001-x").check({ slug: "0001-x", spec: "" }).length; // 1

Source: commons/mizan/src/changes/plugin.ts

0 of 2 exports are imported by a test of the run. A test that imports an export may not call it or check what it returns.

changes.declarationPluginfunctionno test imports it
function declarationPlugin(declaration: Declaration | undefined, file: string, anchor: string | undefined): RulePlugin

The plugin that finds a declaration wrong by itself, reporting it for the specification named anchor only.

declarationPluginfunctionno test imports it
function declarationPlugin(declaration: Declaration | undefined, file: string, anchor: string | undefined): RulePlugin

The plugin that finds a declaration wrong by itself, reporting it for the specification named anchor only.

Titles, headings, exports, tables, columns and requirements. Esc closes.