Validation
Build checks stay visible
WandGx runs multi-layer validation in configured generation lanes, checking for broken dependencies, launch errors, dead pages, and accessibility issues before preview, publish, or source readiness is claimed.
What validation checks
Validation runs in configured build lanes. This is what gets checked.
Dependency integrity
All imported packages are resolved and present in the manifest. Missing or mismatched dependencies are flagged.
Render error detection
Static analysis and build-time execution surface common launch errors before readiness is claimed.
Page completeness
Page links can be 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 source safety
Source errors and data-shape mismatches between app screens and services 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 treated as ready for preview, publish, or source handoff. Warnings are flagged for your attention. 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 ready, publish, or source claims until the build is rerun or flagged for your review.
Can I see the validation report for past builds?
Builds that run validation keep a report in the project detail view so you can inspect the evidence behind readiness claims.
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 code checks?
WandGx validation goes beyond type checking. It includes rendered behavior testing, link verification, accessibility auditing, and dependency resolution — all run automatically after generation.
Related