Repository navigation
Ratchet Studio Pro checker warnings (and Best Practice Recommender if headless) #351
Description
Source: external reviewer feedback (2026-10-14).
Now: we ratchet mxcli lint findings. mx check blocks only on errors; its warnings are not ratcheted.
Proposal: capture the mx check warning count per code into a baseline, and fail on a rise (same model as lint-gate). Probe whether the Best Practice Recommender can run headless; if it can, ratchet it too.
Value: medium-high.
Generated by Claude Code
Activity
MendixMau commentedon Oct 14, 2026
Gain test case
Metric: new Studio Pro checker warnings that reach the gate unnoticed.
mx checkoutput before and after a script that adds a known warning (e.g. an unused variable, an empty validation message).Generated by Claude Code
MendixMau commentedon Oct 14, 2026
Tier: every exec (seconds budget). The Studio Pro warning ratchet runs on every exec, beside the lint ratchet. This applies per
skills/testing-shape.md§3 "Check tiers" once #364 lands. Until this issue is built, the table marks it as "(planned: #351)".Generated by Claude Code
MendixMau commentedon Oct 14, 2026
Correction to my comment above: review of #364 renamed "tiers" to check moments, so that it does not collide with
testing-shape.md§1's "No tiers". This issue sits in the every exec moment, which has a budget of about 1 minute because mxbuild dominates it. The placement itself is unchanged.Generated by Claude Code
Merge #364: process(testing): three check tiers — every exec, module …