Fix: Handle non-Date objects in DateUtil.clone#457
Open
winnyboy5 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.