Invalid date exception handling

[laputaworkuk]

Hi ,

If I input invalid date time value, e.g. 23/13/2023, it will only throw
Error: TD: Could not correctly parse "23/13/2323" to a date for input.
at ErrorMessages.failedToParseDate
How can I catch this error ?

Thank you

[Eonasdan]

The errors are described in the docs. Each has a "code" you can look for. If you need to handle None US dates see the custom date format plugin

[iainworkman]

Is there a particular pattern for catching these errors?
I tried

const tdInput = new tempusDominus.TempusDominus(document.getElementById('tdInput'))
tdInput.subscribe(tempusDominus.Namespace.events.error, (event) => {
  console.log('default date error thrown')
})

...but that never seems to get caught. Other than that I can catch this at a window level (window.onerror = () => {}) but that seems a touch heavy-handed.

[Eonasdan]

Yeah I think I need to work on a better was to do those errors. I don't have any good ideas at the moment though.

[Eonasdan]

This is done in 6.9.4

[Niddrym]

Here is a hacky method involving overriding the parseInput function that worked for my use case:

date.dates.oldParseInput=date.dates.parseInput;
date.dates.parseInput=(input)=>{
  try{
    return date.dates.oldParseInput(input);
  }
  catch(err){
    date.dates.clear();
  }
};

Technically the documentation does say you can override the parseInput method.

[axunonb]

Very good, this worked for me, too. Maybe good to know that with date the tempusDominus.TempusDominus instance is meant.
@Eonasdan : Wouldn't this issue deserve a hot fix to v6.7.7?

[Splines]

@Niddrym Thanks a lot, this worked, although it is rather hacky to hook that deep into the library code. Hopefully, we will get a more convenient way to catch errors eventually. This method may fall apart quickly if something changes internally in the tempus dominus code.

[Eonasdan]

Please make sure you follow this #2793

[Eonasdan]

This is done in 6.9.4

[Eonasdan]

This is done in 6.9.4