-
-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pass through more fields #90
Comments
Ah, thanks for raising this @pcause . Based on your description I see these fields:
Anything else? |
@pcause - what calendar provider are you using that supports vtodo? I tried Google Calendar and as far as I can tell, they don't include tasks as vtodo entries. |
I am not sure I am using yet, but on MS365 and hoping MS Todo might. |
From searching the interwebs, I saw that Outlook doesn't support VTODO so I doubt it. Let me know if you find a server/client and I'd be happy to figure out support (as I'd love to use it too!) |
For those of us scripting the format, could you pass through additional fields. I've like the free/busy (I can use css to color differently in my script). Think you should also add an element to the IEvent structure to say if a vevent or vtodo and allow an option for also handling vtodos which you now skip even though the data structure for ics parser handles both . this allows scripters to handle external todos from ics sources. I wouldn't pass the vtodos through to the simple interface just for scripters.
The text was updated successfully, but these errors were encountered: