You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't researched this in detail yet, but there seems to be a difference in the shape of notifications for PRs and for discussions.
Earlier today I had three notifications in my inbox, 2 from discussions and 1 from a PR. When trying to fetch all notifications I received this error:
ParseError "Error in $[0].subject.url: parsing URL failed, expected String, but encountered Null"
I marked one of the discussion notifications as done, ran my code again and got the same parse error. Then I marked the second discussion notification as done, and when I ran my code after that it happily parsed the response with a single PR notification.
The text was updated successfully, but these errors were encountered:
Now I've made a small change that solves the issue for me at least. This does go against the documentation, so arguably it should be pointed out to GitHub/Microsoft too.
Yeah, also for GitHub actions in the notifications the subject url can be null. According to the published spec by github we are already not correct because subject "last comment url" is also often null, which this library apparently accepted.
I haven't researched this in detail yet, but there seems to be a difference in the shape of notifications for PRs and for discussions.
Earlier today I had three notifications in my inbox, 2 from discussions and 1 from a PR. When trying to fetch all notifications I received this error:
I marked one of the discussion notifications as done, ran my code again and got the same parse error. Then I marked the second discussion notification as done, and when I ran my code after that it happily parsed the response with a single PR notification.
The text was updated successfully, but these errors were encountered: