Skip to content

Fix: Handle non-Date objects in DateUtil.clone #457

New issue

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

winnyboy5
Copy link

The DateUtil.clone function previously relied on date.getTime(), which would throw an error if date was not a valid Date object. This could occur if a string, number, or other unexpected data type was passed to the function.

This commit makes DateUtil.clone more robust by handling non-Date objects. The function now checks if the input date is a string. If so, it attempts to parse the string into a Date object using Date.parse(). This allows the function to handle date strings correctly.

This change prevents runtime errors and improves the reliability of DateUtil.clone when dealing with various input types.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy