task by index not working outside of context

[naggie]

The default command, next should ignore the context if a task is referenced to be viewed by ID, much like the edit or note commands which work regardless of context if an ID is provided.

[naggie]

@dontlaugh this may be awkward to fix with the current filtering mechanism which sees a combined context and command line filters.

Perhaps the solution is not only ignore the context when an ID is provided, but the rest of the query too. We should probably also throw an error if an ID is specified together with command line filters.

[dontlaugh]

I think you are right. I will try sketching out this solution:

• if IDs and cmdLine tags or projects are passed, we error. This has the benefit of being catchable immediately after parsing, before a command is even selected
• of course, context tags will be allowed, since those could be set in the environment.
• if IDs are passed, we do not need to enter the filtering loop at all, we can take another code path and return early. This will ignore any other attributes in our query, as you describe

[dontlaugh]

Actually, it would be cleaner (and reasonable?) to validate the options passed to NewTaskSet, as well. I will try to do that.

---

Update: After thinking about this, I think it's simpler to do this validation in func main, for now. The reason is that NewTaskSet does not have a way to differentiate between tags and project strings passed from context vs. command line. And I have a hunch that it would be good to keep those concerns separated. 🤔

[naggie]

thanks to @dontlaugh -- fixed by #62