[fix] timesheet entries that fall on midnight were not included #2497
Conversation
This file contains 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
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.
Link to ticket
Fix for api rate limiter call #2495 (as of 3.1.3)
Fix for timesheet comparison error
Description
This fixes 2 bugs. One that was introduced with the ratelimiter in 3.1.3 causing a call to undefined method error and the second one a bug around timesheet management for dates that fall exactly on midnight.
Screenshot of the result
If your change affects the user interface, you should include a screenshot of the result with the pull request.
Checklist
If your code does not pass the requirements on the checklist, you should add a comment explaining why this change
should be exempt from the list.
Additional comments or questions
If you have any further comments or questions for the reviewer, please add them here.