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.
I've made valuable improvements to the timelydiff function. Firstly, I enhanced error handling to provide clearer messages for invalid input. Now, if someone tries to use the function with a timestamp in the wrong format or if the length parameter is not a string, they'll get a helpful error message.
Moreover, I added a fantastic feature – users can now customize the date format! Whether they prefer the default format, 'dd/mm/yyyy', or 'mm/dd/yyyy', they have the flexibility to choose. This enhancement makes the function more user-friendly and adaptable to different needs.
I've thoroughly tested these changes on a separate branch ('enhance-timelydiff') to ensure a smooth integration. I believe these enhancements will make the timelydiff function even more versatile and user-friendly.