Validating with check

Run buildprint check before every buildprint apply. Check validates the pending workspace changes against Buildprint's filesystem, schema, reference, workflow, expression, layout, and project-test rules.

buildprint check

Default scope

By default, check compares the workspace to the current Bubble snapshot for the branch and validates the changed files. Changed canvas files are expanded to the relevant canvas root so element and workflow relationships can be checked in context.

There is no all-files flag today. To satisfy buildprint apply, run the unfiltered command:

buildprint check

A successful unfiltered check records a freshness fingerprint for the current Bubble baseline and the current pending changes. apply uses that record to make sure nothing changed after the check.

Target specific paths

You can check specific workspace paths while editing:

buildprint check pages/home/page.json
buildprint check pages/home/elements/card
buildprint check tests/smoke/checkout.json

Directories include files beneath them. Explicit path checks skip workspace-wide rules and do not record the freshness marker required by apply. Use targeted checks for fast iteration, then run plain buildprint check before applying.

JSON formatting and autofixes

Check formats changed JSON files before running rules. If canonical formatting changed a file, the report includes that autofix information. Review git diff after check if you want to see formatter changes.

Filtering rules

buildprint check --rule canonical-form
buildprint check --rule 'children-manifest/*'
buildprint check --level warning --json

• --rule <id> runs only a rule with the exact id or a prefix pattern ending in /*.

• --level <error|warning|info> controls the minimum severity printed. The default is info.

• --json prints the report as JSON.

Rule-filtered checks are useful for debugging, but they do not satisfy apply freshness.

Expression schema hints

When check finds expression-related issues, it may write an expression schema hints artifact and print the artifact path. Use that file to inspect expected expression shapes while fixing the issue.

Auto-apply

buildprint check --auto-apply

--auto-apply runs apply immediately when the unfiltered check has no blocking error-level issues. Warnings and info findings do not block auto-apply.

--auto-apply cannot be combined with --rule, --json, or explicit paths.

Exit behavior

If check finds any error-level issue, it exits non-zero and prints Check failed: errors present. Fix the reported files, rerun buildprint check, then apply.

If there are no changed files, check prints No changed files. No checks run. and --auto-apply skips apply.