The check

The check builds the description of a project, carries out every rule on it, and answers every finding at once. It never stops at the first, and it changes no file but the type list of the project. checkProject of forjr/check does it, and forjr check is a few lines over it.

import { checkProject } from 'forjr/check'

const { findings, forms, why } = await checkProject('./my-app')

A program that builds each save runs the two halves of the check apart, as command.dev does. rulesOver({ description, source }) carries out our own rules over what a build just read, and reads no file. keepTypes(folder, source) starts the type checker and keeps it running: next() answers what its next pass reported, and stop() ends it.

The two layers

Our own rules read the description and the source, and finish in well under a second. The type checker then reads the whole project, as a program of its own, with forjr.d.ts written anew first. Each of its findings is code.F8000.

The levels

An error blocks a build: no bundle is written. A warning and a note do not.

The groups

The other groups arrive with the parts they hold: flows, and connecting out.

The type checker reads the screen files too. Where it says that a name does not exist on a row, the finding ends with the table and its columns, as: The table customers has the columns id, createdAt, updatedAt and name.

Options

facts are what only a running app knows, as the findings of a table change against its data. The check opens no database: whoever calls it passes them in. forjr check asks the engine that runs on the data of the project, and readFacts of forjr/engine where none runs. The rules of code.F2001 to code.F2004 pass on what the facts hold, and add the place of the table in the source.