8

Allow profiles with no associated tasks.

Doing so would allow conditions to be named for easy use only for Profile Active State triggers.

The current workaround it's to have such profiles associated with a "No Op" task.

3 replies

NY

Not just run log pollution but pollution in general. Just as one would avoid writing code that does absolutely nothing since it adds noise, the same holds for profile definitions.

At the end of the day, calling a No Op task is a workaround and a hack to a limitation of the tool. Rather than having this workaround/hack proliferate, best would be to fix the tool such that the workaround/hack is no longer needed.

TP

Is there anything wrong with using a "No Op" Task?

I just have one with a single Anchor/label:

  • A1. Anchor: "Nothing to see here"

Nothing huge wrong with a dummy task, but that task pollutes the run log with three unneeded lines. It possibly also runs a but slower than if Tasker knows to not run a task at all.

I think that ultimately the problem is that some information Tasker has access to is only available via profiles rather than also variables.