inertia-form-review

To audit Inertia.js forms for i18n compliance, run a targeted scan against resources/js/pages and related locale files. This identifies translation gaps in labels and error messages, detects missing validations, and generates an actionable remediation report.

Ensuring type safety between Inertia forms and Go API contracts requires validating that TypeScript types align with backend structures. This process verifies type-safe data structures, flags free-text foreign key fields, and enforces strict typing across your form components.

Yes, you can check Inertia forms for accessibility automatically. The audit verifies proper ARIA attributes, label associations, and required indicators across your form components to ensure compliance and consistent user experience for all users.

Maintaining UI parity between create and edit flows involves auditing the forms to enforce consistent layout and behavior. The audit compares both views within resources/js/pages to identify discrepancies and provides remediation guidance to align them.

Yes, the form audit works with both TypeScript types and Go request structures. It validates alignment between frontend TS types and Go/API contracts to ensure strict typing and verify that no free-text foreign key fields exist.

Inertia form translations show missing keys when labels, placeholders, or error messages bypass translation files. An i18n compliance audit scans related locale files to identify these exact translation gaps and enforces the usage of proper translation keys.