The GitHub UI on github.com/notifications only shows the notifications you haven't pressed "done" on.
Whereas the REST API call for /notifications returns only the unread ones by default. Or, if you pass "all=true", you get all of the notifications, whether "done" or not.
There seems to be no way to match the web UI's behavior using only the REST API.
It may be possible if we use GitHub's GraphQL API.
Could also potentially do a hack where we fetch pages as needed until we accumulate enough non-done notifications to display, but we wouldn't be able to get the total number of pages. -- This wouldn't work because we don't even get a working "done" field.
The GitHub UI on github.com/notifications only shows the notifications you haven't pressed "done" on.
Whereas the REST API call for /notifications returns only the unread ones by default. Or, if you pass "all=true", you get all of the notifications, whether "done" or not.
There seems to be no way to match the web UI's behavior using only the REST API.
It may be possible if we use GitHub's GraphQL API.
Could also potentially do a hack where we fetch pages as needed until we accumulate enough non-done notifications to display, but we wouldn't be able to get the total number of pages.-- This wouldn't work because we don't even get a working "done" field.