SmsFormValidationService looks up a requiredTrue error key for the agree/consent control, but Angular’s Validators.requiredTrue emits { required: true }. The “You must agree…” message therefore never surfaces via validateForm.
Either map required → the agree message for that control, or use a custom validator that sets requiredTrue.
Impact
Users can fail validation without seeing the intended consent error copy.
## Summary
`SmsFormValidationService` looks up a `requiredTrue` error key for the agree/consent control, but Angular’s `Validators.requiredTrue` emits `{ required: true }`. The “You must agree…” message therefore never surfaces via `validateForm`.
## Found by
Wave 6 coverage tick 7 a3 — SMS form-validation specs (`ce1736f4`).
## Expected
Either map `required` → the agree message for that control, or use a custom validator that sets `requiredTrue`.
## Impact
Users can fail validation without seeing the intended consent error copy.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
SmsFormValidationServicelooks up arequiredTrueerror key for the agree/consent control, but Angular’sValidators.requiredTrueemits{ required: true }. The “You must agree…” message therefore never surfaces viavalidateForm.Found by
Wave 6 coverage tick 7 a3 — SMS form-validation specs (
ce1736f4).Expected
Either map
required→ the agree message for that control, or use a custom validator that setsrequiredTrue.Impact
Users can fail validation without seeing the intended consent error copy.
Resolved in spikersoft-angular PR #819 (merged to
master). SmsFormValidationService requiredTrue matches Angular {required:true}. Closing.