Due to Marvin API beta limitations, the only available tasks to connect to are tasks that are scheduled for the day, and tasks that are due for the day.
I propose a workaround (until the Marvin API gets finalized and more robust) where a local copy of today's scheduled tasks and due tasks are created each day the plugin is in use. That way, a running log of tasks could be created.
The local copy of today's tasks could have a user-customizable format, so that one could format it to use in conjunction with (https://github.com/schemar/obsidian-tasks)
Due to Marvin API beta limitations, the only available tasks to connect to are tasks that are scheduled for the day, and tasks that are due for the day.
I propose a workaround (until the Marvin API gets finalized and more robust) where a local copy of today's scheduled tasks and due tasks are created each day the plugin is in use. That way, a running log of tasks could be created.
The local copy of today's tasks could have a user-customizable format, so that one could format it to use in conjunction with (https://github.com/schemar/obsidian-tasks)