How can I use Validators.mustMatch in the @FormControlAnnotation() ? about reactive_forms_generator HOT 5 CLOSED

Hi.
Check the updated example
4b03e55

from reactive_forms_generator.

There is no ability to access parent in current implementation.
you can refer to statically generated control names in your validators
https://github.com/artflutter/reactive_forms_generator/blob/master/packages/reactive_forms_generator/example/lib/docs/login/login.gform.dart#L180

from reactive_forms_generator.

@vasilich6107 Is there a way to obtain the generated form object from a form control? That would allow operating on the controls safely. Otherwise, you kinda lose the benefits of code generation (control names, casting types, finding nested controls).

from reactive_forms_generator.

hi. The thing is that

'Prefer not to call `model` on non-valid form it could cause unexpected exceptions 
in case you created a non-nullable field 
in model and expect it to be guarded by some kind of `required` validator.',

Let's say you have String(non nullable field) in your model, it is guarded by required validator.
at the time you are calling mustMatch the counterpart field could be null and it will have an exception due to the casting of String? to String

from reactive_forms_generator.

Thanks @vasilich6107 I see what's the concern. I think I'm not talking about reading form model values from a control but, rather than that, accessing other field controls in a typesafe way. So instead of doing:

FormControl<Field2ValueType> getField2Control(FormControl field1Control) {
    final formGroup = field1Control.parent as FormGroup;
    final field2Control = formGroup.control('field2ControlName');
    return field2Control as FormControl<Field2ValueType>;
}

There would be something like:

FormControl<Field2ValueType> getField2Control(FormControl field1Control) {
    return field1Control.parent.field2Control;
}

I guess that's a completely new feature (assuming it would be possible) and not a trivial change.

from reactive_forms_generator.