-
-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could the 5 Status Types be included in the CSS? #1811
Comments
/CC @esm7 for info... |
Perhaps I'm misunderstanding the request here, but to my understanding you can use the |
If this does help with what you mean, can you elaborate what kind of styling per status type you would like to achieve? |
Good question. Thanks for asking. ContextHere are my statuses: And here is some vocabulary, if you haven't used the custom statuses: Short-termSo I should start by restating my question as: What would a selector look like that selects the following status symbols, which would select my TODO and IN_PROGRESS tasks:
If that is currently possible, it would certainly get me going for now, and I could document it. Longer-termDifferent users will use different symbols to denote TODO, IN_PROGRESS, DONE, CANCELLED and NON_TASK tasks. If anyone were to want to sharing styling that did different things for different task status types, they couldn't reply on the actual status symbols, and would need to base the styling in the type instead. |
Technically it is Regarding the longer-term, it is straight-forward to add another data attribute with the Task Status Name. At the end of |
Sure, I would like to fix a problem that when I use the 'overdue' example from the docs, in reading mode 90% of my tasks are highlighted because I already either did them, or cancelled them. So I like to be able to:
Thank you. I think I would then add OK, if by any chance you had time to submit those, it would be a great help. If not, I'll try and get them done towards the back end of next week. I can't do anything on this for the next few days anyway. So I'll ponder whether to add a note to the documentation, recording the current limitation - or whether to release when the overdue styling can be written in a way that's useful for real-world-use. |
Modifying the
You can add more custom statuses to this selector by duplicating the complete line, writing another rule for
I don't mind looking into adding |
D'oh. Thank you very much. I think I will have to write a 'how-to' guide, for my own education and use - and keep the
Wonderful. Thank you. The name and type are other values alongside the If the selectors are case-specific, please do stick to all-caps, like TODO, as that is what is visible to users in the docs. |
Oh sorry, yes, no problem using the same branch, if it helps... |
But do look at the diffs between your branch and |
Merged from main to get the most up-to-date docs, then added attributes for custom statuses + documentation + tests. |
After merging the last commit on
|
Thank you! notes to self:
|
Thanks. FYI Another time I would ask for a new branch to be created. Either WebStorm or me has got totally confused by me creating a PR from a branch on your fork. I'm going to merge it sight-unseen and then test it on main and make documentation changes in a second PR. |
🔖 Feature description
I'm trying to style loads of tasks and I have a variety of different custom statuses, so as far as I can tell, the only real information to tell me whether the task is done, todo, cancelled etc is the Task Status Type.
https://obsidian-tasks-group.github.io/obsidian-tasks/getting-started/statuses/status-types/#overview
✔️ Solution
Could the status types be included as data attributes in the generated CSS?
❓ Alternatives
No response
📝 Additional Context
No response
The text was updated successfully, but these errors were encountered: