isValid throws console.warn when pass the string

I’m trying to check the date is valid or not with isValid and it returns false when I pass the string eg. ‘2016-01-01’ But toDate function is still logging the two console warnings

First one: Starting with v2.0.0-beta.1 date-fns doesn't accept strings as arguments. Please use "parseISO" to parse strings. See: https://git.io/fjule

Second one: Error at toDate (index.js:50) at isValid (index.js:68) ...

I don’t know it’s intended or not but IMHO toDate should not throw warnings when isValid used.

[ropinheiro]

I should also add to this that maybe date-fns should throw exceptions instead of polluting the console with warnings. I’m doing some code that try-catch a format() attempt, as I can’t be sure if the data I receive is a valid date or not (it can be a valid date, or a string with a valid date formatted, or a string that must pass as-is), then in the catch I handle the invalid cases. The problem is that, although my code works pretty well, date-fns constantly fills the console with huge dumps each time format function isn’t able to format the date. The catch prevents the exception to be written in the console, but the format function writing warnings escapes to my control. Isn’t there a “quiet” option to make it behave silently?

[Fortidude]

Well… passing it with parseISO makes no sens…

https://date-fns.org/v2.9.0/docs/isValid

Name	Type	Description
date	*	the date to check

you should change the documentation, or remove the error and just return false. Ofcourse in my opinion.