search

sawhney17 / logseq-calendars-plugin

MIT License
128 stars 17 forks source link

MS Teams invited meetings populating incorrectly #45

Open jegillikin opened 1 year ago

jegillikin commented 1 year ago

Anytime I receive an invitation to a meeting through Microsoft Teams, the plugin imports the times incorrectly and uses odd placeholders ("object Object") in place of the actual meeting attributes. Of note, I'm subscribed to Proton Calendar via iCal and the feed allows full access to the calendar's data.

I duplicated the meeting by hand in Proton Calendar and re-imported so you can see how these look:

CleanShot 2023-05-02 at 10 07 39@2x

Currently running LogSeq 0.9.4 on macOS 13.3.1, with the most current version of the plugin available through the Marketplace.

As far as I can tell, this glitch only occurs when I'm served up a meeting via Teams. Proton Calendar doesn't seem to balk at anything (all the calendar's metadata fields are correctly populated) so I'm curious as to whether this is a parsing problem either in the API feed from the calendar, or by the plugin as it translates the feed into LogSeq.

I should add, I also have this calendar feed subscribed in Apple Calendar and it shows up just fine.

jegillikin commented 1 year ago

This might be related to #7 -- I wonder if the timezone offset is being applied to the start time, but not the end time, and thus "it's ending before it starts" causes the rest of the record to fail?

(All of my Teams meetings are scheduled by a project manager two timezones away -- Mountain Time, vs. me in Eastern.