GCalToolkit / Sheets2GCal

Issue Tracker for Sheets2GCal Google Sheets Add-on
0 stars 1 forks source link

End Date in Google Calendar does not match End Date in Google Sheets #18

Open TKaur85 opened 1 year ago

TKaur85 commented 1 year ago

The end date is consistently showing up as a day earlier in the calendar than what is entered in Google Sheets. For example, if an event takes place from Dec. 10 to 12 in Google Sheets, in the Google Calendar Event it only registers as Dec. 10 to 11.

GCalToolkit commented 1 year ago

End dates in Sheets2GCal for multi-day events are exclusive to conform to the iCal standard and the way Google Calendar stores event data.

If it helps to understand this, an all-day event is commonly defined as 00:00 to 00:00 the next day, so a one day event on June 1st is defined as starting June 1st 00:00 and ending June 2 00:00.

As a programmer I always use exclusive end dates and released Sheets2GCal like that - only later did I realize that most people consider end dates to be inclusive... by which time making this change would break sheets for everyone already using Sheets2GCal.

So, for now I'm afraid you need to use exclusive end dates (i.e one day later). I made a special exception for single day events so you don't need to add a day for an event on the 10th; for an event on the 10th you can use 10th - 10th, or 10th - 11th, or even just 10th.

Finding a solution is on my Todo list, but I haven't yet figured out how to manage this for existing/new Sheets without breaking everything for existing sheets.

I will probably eventually add an option when creating new Sheets2GCal Sheets to ensure that existing Sheets are not affected, with an option to convert existing Sheets to the "inclusive end date" format.

I'm sorry about the inconvenience this causes, and will let you know here as soon as I come up with a satisfactory solution.

TKaur85 commented 1 year ago

Thanks for the timely response.

Now I know I can implement my own solution. I am linking the sheet to cells in another sheet, so I will add +1 to my formula, which solves the problem.

And yes, I’d appreciate communication if there is an an option created for inclusive end dates.

On Wed, Nov 23, 2022 at 3:03 PM GCalToolkit @.***> wrote:

End dates in Sheets2GCal for multi-day events are exclusive to conform to the iCal standard and the way Google Calendar stores event data.

As a programmer I always use exclusive end dates and released Sheets2GCal like that - only later did I realize that most people consider end dates to be inclusive... by which time making this change would break sheets for everyone already using Sheets2GCal.

So, for now I'm afraid you need to use exclusive end dates (i.e one day later). I made a special exception for single day events so you don't need to add a day for an event on the 10th; for an event on the 10th you can use 10th - 10th, or 10th - 11th, or even just 10th.

Finding a solution is on my Todo list, but I haven't yet figured out how to manage this for existing/new Sheets without breaking everything for existing sheets.

I will probably eventually add an option when creating new Sheets2GCal Sheets to ensure that existing Sheets are not affected, with an option to convert existing Sheets to the "inclusive end date" format.

I'm sorry about the inconvenience this causes, and will let you know here as soon as I come up with a satisfactory solution.

— Reply to this email directly, view it on GitHub https://github.com/GCalToolkit/Sheets2GCal/issues/18#issuecomment-1325709836, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4LNU6XK53OGBW6XGRHCLNLWJ2IDHANCNFSM6AAAAAASJMHHTU . You are receiving this because you authored the thread.Message ID: @.***>

Emmmm8888 commented 4 months ago

Hi,

Just checking if the option for inclusive end dates is available?

Thank you!

GCalToolkit commented 4 months ago

I'm sorry for the delay, and sadly I still don't have a good solution for this. Displaying the same dates that are actually stored by Google Calendar simplifies a lot of things behind the scenes.

Supporting both methods is potentially dangerous for existing users and could introduce unforeseen bugs. At some point I might just release a completely separate version that does do this, but even then I would have to set up automatic migration for people who want to switch...

So for now I'm sorry to say this is on hold :(