-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
Export to Markdown #369
Comments
Nice! It might be useful to have something like this in core. However there's not really a concept of "cancelled" todos in Markdown 🤔 |
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. |
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. |
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 |
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
The text was updated successfully, but these errors were encountered: