Joan Pablo

Hi @RandalSchwartz, Sorry for the late answer and thanks for your advice. I will take a closer look at your proposition. I will let you know when it is included...

Hi @RandalSchwartz, could you give some examples of valid emails that do not match the current regex implementations (just to create some unit tests) Thanks best regards

Thanks @vasilich6107 I will take a look

Hi and thanks for highlighting the need for a new email validation approach. I believe you are right and we need a new implementation that doesn't use Regex. I will...

Hi @vasilich6107, Mmm yes, you are right, In my opinion, you should not use the method *setError* to set a **null** value. If the idea is to clear all errors...

Mmm, I see @vasilich6107, But, what does this supposed to do? ```dart someField.setErrors(null); ``` 1-) Remove all errors from the field? 2-) Don't do anything at all? And at the...

Also AbstractControl.errors is not nullable, I mean you will always get an instance of a Map, not a **null** value, that's why the setError does not allows setting a null...

Hi @kuhnroyal @vasilich6107 What if we modify the method **showErrors** to something like: ```dart showError: (control, errorName) => control.invalid && control.touched && errorName != ValidationMessage.maxLength, ``` so you will decide...

@kuhnroyal @vasilich6107 @naamapps Yes, I understand that the easy way could be just to define the method to return a String? instead of a String. But what if the developer...

Thanks, @naamapps for your quick response, I got your point. It is just that I'm wondering if it is the right decision or not. I know that in an ideal...