fabiospampinato / vscode-todo-plus

Manage todo lists with ease. Powerful, easy to use and customizable.
MIT License
902 stars 228 forks source link

Export to Markdown #369

Open Indeedornot opened 1 year ago

Indeedornot commented 1 year ago

Hi! I am an avid user of this extension and I was using it to draft my roadmaps for the future To simplify this I've created a github action formatting TODO file into a segment in a README. I plan to work on it more to expand its capabilities.

https://github.com/Indeedornot/todo-to-markdown

fabiospampinato commented 1 year ago

Nice! It might be useful to have something like this in core. However there's not really a concept of "cancelled" todos in Markdown 🤔

Indeedornot commented 1 year ago

I'd love to contribute to the project.

Currently the only way i can think of and have used previously is crossed markdown task text

- [ ] ~~Text~~

Should it not emphasises todos enough the exporter could be rewritten to use emojis provided by the extension or other markdown supported emojis - that however would mean moving away from default list.

I have thought of possibly graying the text out. Sadly from my findings github as of now does not support colors sans for diff and code tags, meaning that either way there would be no way to add colors to the text.

riddlew commented 1 year ago

I would love to see this feature along with completed todos crossed out as shown in @Indeedornot 's example. I love this extension, but I would prefer to keep todo files in repos as markdown files since not everyone uses VSCode and this extension. Being able to convert a todo.md file to a TODO+ file and vice versa would be perfect.

Indeedornot commented 1 year ago

I believe the action itself is for the most part usable, so should you want you can use it from the linked repo

However should there be a way for me to help in implementing it core I'd be happy to help.

There are things to be thought about like correct time parsing or as mentioned cancelled tasks

Would be happy to continue working on it (lately didn't update it due to personal stuff plus the action at this moment seems to be feature completed for my use case)