We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello,
I found a strange behavior (in v17 at least, I didn't try in v18):
When binding a non required form control's input with the mtx-datetimepicke control, it looks like the related form's validity is messed up with.
mtx-datetimepicke
After the first render, the form is invalid even though the target value is not required.
Filling the input with any value and then removing the value makes the form valid again.
I would expect the form to be valid right from the start.
See this StackBlitz sample
The text was updated successfully, but these errors were encountered:
Please use other adapter instead of native adapter #141
native adapter
If you use native adapter, please set default value null
null
form = this.fb.group({ dueDate: [null], });
https://stackblitz.com/edit/nk9byo-uy4zgu?file=src%2Fexample%2Fdatepicker-overview-example.ts
Sorry, something went wrong.
No branches or pull requests
Hello,
I found a strange behavior (in v17 at least, I didn't try in v18):
When binding a non required form control's input with the
mtx-datetimepicke
control, it looks like the related form's validity is messed up with.After the first render, the form is invalid even though the target value is not required.
Filling the input with any value and then removing the value makes the form valid again.
I would expect the form to be valid right from the start.
See this StackBlitz sample
The text was updated successfully, but these errors were encountered: