1. Home
  2. Forum
  3. Angular - EJ 2
  4. Problem with ejs-datepicker improperly dirtying the reactive form

Problem with ejs-datepicker improperly dirtying the reactive form

Hello

I'm having a problem with the ejs-datepicker component. I have a route guard, who handles candeactivate. What happens is that only the date field (ejs-datepicker) is getting dirty in the deactivate. If I switch to any other type of component, be it a textbox or maskedit, it works. There is nothing different. The scenario is as follows: when I enter to edit the data and close it without changing anything it gets dirty. I tried to find something on the web and in the documentation to see if it would be a peculiar behavior of the component, but I found nothing. I thought it could be something related to the life cycle. But no, since all the other fields work and only it is dirty ?!

If you have already noticed this behavior, or have an idea of why it happens, I appreciate the help.

Sincerely

Fabiano Melo
Brazil, Rio Verde, Goiás

3 Replies
SP Sureshkumar P Syncfusion Team August 11, 2020 12:24 PM UTC

Hi Fabiano, 
 
Based on your shared information, we have created the sample and validated the reported issue. But we cannot replicate the reported issue from our end. please find the screen shot and sample below.  
 
Screenshot for same behavior compare with textbox component. 
 
 
 
 
If still you have facing the issue, then please provide the below details. 
1.     If possible, please replicate the reported issue from our above attached sample and provide detailed image or video representation of issue replication steps. 
2.     If, possible, please forward the issue replicable sample to us. 
3.     Please share the Syncfusion package version details. 
These details will help us to provide exact solution as earlier as possible. 
 
Regards, 
Sureshkumar P 
 


FM Fabiano Melo August 11, 2020 01:33 PM UTC

Hello

The problem of the datapicker component getting dirty in deactivate I couldn't solve. However I managed to get around the problem in my deactivate route guard. I noticed that he dirty the field, but kept it as untouched. So I changed my logic, instead of just checking if it was dirty, I check if it is dirty and touched and elsewhere if it is pristine or not touched. Anyway, I got around the problem.

SP Sureshkumar P Syncfusion Team August 12, 2020 11:30 AM UTC

Hi Fabiano, 
 
Thanks for your update. 
 
Based on your shared information. We did not get the requirement clearly. So, kindly update your requirement with image or video representation. That will help us to provide exact solution as earlier as possible. 
 
Note: we have already checked the previously attached sample based on your requirements. But we cannot replicate the reported issue from our end.  
 
Please find the screen shot here: 
 
 
 
Regards, 
Sureshkumar P 


Loader.
Up arrow icon