Checking a task inside a callout triggers an obsidian-tasks warning about obsidian-todoist-plugin HOT 4 OPEN

@jamiebrynes7 Hi, just to add save you a bit of time, what I was suggestion in one of those Tasks reports in this comment:

The Todoist aspect of this issue itself is not something that I personally would investigate alone, for two reasons:

• It involves another plugin: see Bug involving another plugin
• It needs a Todoist account and token to reproduce the bug.

If you can talk to the author of the Todoist plugin and find out if there is any way that other plugins can identify whether a task is in a Todoist code block, that would be helpful.

Once we know that, there's a conversation to be had about whether Tasks should just ignore and tasks that are in a Todoist code block, as in not do any checks for recurring tasks, and not add a Done Date.

from obsidian-todoist-plugin.

Hi @claremacrae, sorry for the (very) late reply on this! It possible to identify a task via CSS classes on the surrounding element. Anything that is a child of either todoist-task-list or todoist-task-container will be a Todoist plugin task.

I don't know how the Tasks plugin identifies task items, but if those don't work, I can add something directly onto the input checkbox directly, let me know!

from obsidian-todoist-plugin.

Hi @jamiebrynes7, thanks for the reply.

What I tell users in the docs about bugs involving another plugin is:

We do not generally work on problems of Tasks interacting with other plugins unless the author of that plugin is willing to work jointly on the problem.

Spending time getting familiar another plugin's settings, behaviour and code would take time away from improving Tasks.

So, if you would be willing to have an online call for me to show you the relevant sections of code in Tasks and see if we can identify a way forward, please send an email to at the address in my profile here.

I'm very busy for the next several weeks, and am usually booked up with several pairing sessions each week - so the sooner we can get a session in the diary, the better.

Hope to hear from you.

from obsidian-todoist-plugin.

I can also show you the reason behind the warning - it's possible you have figured out an alternative solution to that problem - in which this whole issue just goes away.

(The reason I avoid having conversations about this sort of thing via GitHub is that it is just too low bandwidth to be effective, and is prone to time-wasting misunderstandings.)

from obsidian-todoist-plugin.