Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Allow working with tasks that have "other" values
See original GitHub issueCan dataview store the “data-task” attribute for tasks to allow filtering beyond completed?
For example:
- [>] deferred
- [?] still interesting?
- [-] cancelled
- [R] under review
- [!] important
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:10 (4 by maintainers)
Top Results From Across the Web
Interview Question: "How Do You Delegate?" (With Answers)
"I value delegating tasks at work very much because it helps complete assignments quicker. I've also found it instills confidence and motivation ...
Read more >Make Sure Your Team's Workload Is Divided Fairly
Create a culture that values productivity over hours worked by openly praising strong performance.
Read more >How to prioritize work when everything's important - WeWork
1. Have a list that contains all tasks in one · 2. Identify what's important: Understanding your true goals · 3. Highlight what's...
Read more >Create and work with subtasks and summary tasks in Project ...
Create subtasks and summary tasks to outline the task list in your project. Indent and outdent tasks to show their hierarchy.
Read more >Employees Increasingly Seek Value and Purpose at Work
We asked Gartner Chief of Research Chris Howard what more we need to know about the Great Resignation and how progressive organizations are...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can see something like
Where “selector” more broadly is an asynchronous function that allows you to return what the check should be given the task + current state. This may be nice to implement immediately as a workaround until I implement #1048 .
Oh, that’s an interesting idea. Yes, that can be tracked as well. Be aware that Obsidian doesn’t differentiate by default so it may just show up as “checked” in preview.