Replies: 1 comment 1 reply
-
Hi, thanks for using Tasks. It has become too time-consuming to read verbose descriptive text and try and guess what each user wants. First, please read the Grouping docs page and its many examples of custom groups for the various task fields. If you still need help… Please give some text that can copy, containing:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Okay, so I'm trying to figure out how the
.format
works.The example is not really helpful and kinda confusing.
So, I have the following working line
It's intended to group tasks based on the first subfolder following root.
However, visually they all have the
/
at the end, which isn't the prettiest, but I could live with.More importantly tho, I do have tasks in files that are in the root folder, and while grouping them I'm completely fine with and that's even semi-intended, in the query they are simply labeled as
undefined
. Understandable, since that's what.at(1)
returns since they're in the root.But instead I would simply like to give them a pre-defined heading (like simply "Notes").
Of course the fancier and "over-engineered" version would be to use the root folder's name, but that's a whole different can of worms.
While writing this and looking at it some more, I'm realising
format()
might actually be not at all what I'm looking for, and it instead being the javascript functions that formats input into readable text.But this throws up even more questions on how to achieve what I'm looking for, and if it can even be done?
Beta Was this translation helpful? Give feedback.
All reactions