Validation
Every build is automatically
validated
WandGx runs a multi-layer validation pass on every generated build — checking for broken dependencies, runtime errors, dead routes, and accessibility issues — before you ever see the output.
What validation checks
Validation runs automatically on every build. Here's what gets checked.
Dependency integrity
All imported packages are resolved and present in the manifest. Missing or mismatched dependencies are flagged.
Runtime error detection
Static analysis and build-time execution detect common runtime errors before you ever run the code.
Route completeness
Internal links and routes are verified. Dead links, missing pages, and broken navigation are surfaced.
Accessibility basics
Alt text, ARIA attributes, keyboard navigation, and color contrast are checked against WCAG 2.1 AA standards.
Build success
The project is compiled end-to-end. A build that cannot compile is rejected before delivery.
Schema and type safety
TypeScript type errors and schema mismatches between frontend and backend are detected and reported.
How to read your validation report
Each issue in the validation report includes: the check category, severity level (critical / warning / info), the affected file and line number, and a plain-English description of the problem and suggested fix.
Critical issues must be resolved before the build is delivered. Warnings are flagged for your attention but do not block delivery. Info-level items are suggestions and best practice notes.
Access your full validation report from the project detail view. Past reports are stored with each build version.
FAQ
What happens if validation fails?
You receive a detailed validation report listing each issue, its severity, the affected file and line, and a suggested fix. Critical issues block delivery — the build is rerun or flagged for your review.
Can I see the validation report for past builds?
Yes. Every build in your project history includes a validation report accessible from the project detail view.
Can I disable specific validation checks?
Some checks can be suppressed at the project level for legitimate exceptions — for example, disabling specific accessibility rules for a known trade-off. This is configured in build settings.
How is validation different from standard TypeScript compilation?
WandGx validation goes beyond type checking. It includes runtime behavior testing, link verification, accessibility auditing, and dependency resolution — all run automatically after generation.
Related