Closed jgkamat closed 7 years ago
Only getting unread notifications is certainly possible and I can easily make that the behavior. What surprises me is the sheer number of notifications you have – I can never get more than 15 or so (read or unread) to show up, so I never experiences this usability issue.
Aside, only unread notifications should be expanded by default. Can you kill the buffer and reopen the dashboard? Are they all still expanded? That shouldn't be the case.
What surprises me is the sheer number of notifications you have – I can never get more than 15 or so
I'm not sure what consitutes as an 'unread' notification by the github API. I have had a lot more unread notifications in the past, maybe there's some sort of time cutoff. I watch a lot of repos :P
Aside, only unread notifications should be expanded by default. Can you kill the buffer and reopen the dashboard? Are they all still expanded? That shouldn't be the case.
They are definetly still expanded by default when running magithub-dashboard for me, is there any debug information I could provide that would help with that? :)
Why my command magithub-dashboard
is not available after upgrade package magithub
?
@stardiviner try (require 'magithub-dash)
.
Maybe an autoload on the function could be added to make it easier
@vermiculus Can you add autoload cookie ahead of function?
@stardiviner it's already there
magithub now hides read notifications by default, so I'm closing this. Feel free to reopen if this is still being worked on :)
Continuing from #150
The 'normal' github notification system only shows unread notifications by default (unless you ask for them).
Here's a screenshot of the dashboard (which I think is the full dashboard now)
This is pretty unusable, since I've already seen all the notifications on the screen, and the notifications go down for a long while. A easy improvement for UX (I think) is collapsing the headers by default:
.
However, this is still pretty painful (trying to find unread notifications) After scrolling down a long while, I came up with some of my unreads:
Another easy fix for this is to sort by newest first. I don't particularly like this because it encourages you to leave notifications un-attended for a while, but it is an easy fix.
A better fix (IMO) would be:
OR:
I like the first option more, since it would make opening it faster.
What are your thoughts on the issue? I'm not too familiar with the github API, so I'm not sure if getting only unread notifications is possible.