[Plugin Idea] Support for iCalendar FIles

[zefr0x]

Is your feature request related to a problem? 😢 Please describe.
dooit doesn't have any standard method to save and open todo data. To sync them between my different devices (where dooit might not be usable) and multiple different management tools, we need one.

Describe the solution you'd like 🤔
Implementing the icalendar files support, maybe optionally by enabling an option and specifying a directory to read from and write to. Most other todo tools support it and we could sync it using CalDAV.

Additional context 📝
todoman is a CLI tool that implements it.
python-icalendar and python-ics might help implementing this.

[kraanzu]

Hi there! I didn't know about Caldev. Thanks for sharing this!

Indeed I got a lot of suggestions to implement something that'd integrate dooit with other tools and I'm working on a plugin system that could achieve this using python scripts!

Something like this:

class Plugin:
   ...

    def pre_process(self) -> None:
        # All the pre-processing stuff happens here
        # After it's done, mark the `ready` param as True
        pass
        self.ready = True

    def run(self) -> bool:
        # Do your magic here!
        # Return True to call again else return False
        return False

    def run_on_exit(self) -> None:
        pass

It would make it really easy to implement when dealing with simple text files in the local system as well as communicating with APIs online :D

Edit: I know my previous implementation was too naive and I mixed a lot of frontend and backend stuff together... Dooit will now have a separate API to interact with the todos :D

[kraanzu]

If the icalendar files are parseable, then dooit can use its API to add those. I don't have any plans to implement it right now. Hopefully someone can make a plugin

[github-actions]

Did we solve your problem?
Glad we could help!

Consider sponsoring my work through github sponsors 😄
– @kraanzu

[mathstuf]

Could you leave it open with a label like accepting-patches or the like? I imagine duplicates will be opened over time and being able to keep them together would help those interested all keep track of any status updates on a single issue instead of being spread out. Thanks.

[kraanzu]

I guess creating a separate repo/discussion would be great? Or I can do labels as well

[mathstuf]

A discussion thread could suffice I suppose. My concern there is that they don't show up in issue/PR searches (by default? ever?). But it's better just an old, closed issue.

[kraanzu]

ok fair enough!