-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
Handle subtasks and subgroups (nested lists) in a nicer way #36
Comments
Good point, I didn't know about the possibility of creating a group of lists 😆 I still haven't found a way to access this property. If I find anything new I'll post it here. |
Another thread indicating that unfortunately it is not yet available in the Apple API: I'll check if there's anything new in the new macOS 13. |
In #90 the URL information saved in a reminder was not publicly available in an Apple API, but despite that I found a workaround on the internet to access that value and it worked. I believe the same can be done for nested-lists/subtasks 🤞 This was the change to access the URL info: It is still necessary to investigate the reminder objects to try to fetch this information. I'll try to find some free time to investigate this and add this improvement. |
With the announcement of interactive widgets for iOS, iPadOS and macOS did you found any changes in their API for subtasks? The native widgets only show the number of subtasks but not the subtasks itself unfortunately. |
@pottersfield Apple still doesn't provide an API for subtasks, but I'm doing a workaround to access this information (as shown in the picture in the post above). |
looks good! |
Just wondering if there's any update on this? |
Right now it does not show the top level group in the filtering list, which makes it a little confusing.
Depending on what is available in SwiftUI, a fix for this could either be adding a "Group" to the dropdown of some sort, or failing that, just prefix the list with the group: "Group -> List" in the filter list.
The text was updated successfully, but these errors were encountered: