Fix calling toGMTString on lastModified #277
Merged
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.
This fixes #276.
Function
checkNotifications
is always passed a string value forlastModified
(unless,localStore
is empty, in which case aDate
object is created), so callingtoGMTString()
resulted in an error.This change does the following:
toGMTString()
calllastModified
is always a string, even whenlocalStore
is emptytoUTCString()
as it is more consistent with how JS interprets time.