We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description Not getting the red square on the notification bell upon a new post in a subscribed territory.
Steps to Reproduce Sub to territory, wait for post in said territory.
Expected behavior Red square upon new post, like when a subscribed stacker posts something.
Screenshots Today I subbed to a couple extra territories to be sure of the bug, no red square when these were posted.
Environment: Browser (Brave and Chrome) and PWA
Additional context Has been doing this to me for a while actually:
https://stacker.news/items/441695/r/OneOneSeven?commentId=442970 https://stacker.news/items/430488/r/OneOneSeven?commentId=430959
The text was updated successfully, but these errors were encountered:
I forgot to add a corresponding query to the user.hasNewNotes resolver in #745
user.hasNewNotes
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Description
Not getting the red square on the notification bell upon a new post in a subscribed territory.
Steps to Reproduce
Sub to territory, wait for post in said territory.
Expected behavior
Red square upon new post, like when a subscribed stacker posts something.
Screenshots
Today I subbed to a couple extra territories to be sure of the bug, no red square when these were posted.
The screenshot below did have a red square, because of the subscribed stacker
Environment:
Browser (Brave and Chrome) and PWA
Additional context
Has been doing this to me for a while actually:
https://stacker.news/items/441695/r/OneOneSeven?commentId=442970
https://stacker.news/items/430488/r/OneOneSeven?commentId=430959
The text was updated successfully, but these errors were encountered: