Specify the query parameter orderBy to fix the order of Gcal events at each fetch #32
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.
Hello,
I observed the following behavior: after each sync, the order of events that are already known by Gcal is turned upside down, roughly depending on the last modification date stored by Gcal for each event.
As it is somewhat distracting for the user, I propose this small patch which ensures that the order of events fetched from Gcal is stable. (Namely, events are now ordered by increasing start date.)
Best regards.