-
Notifications
You must be signed in to change notification settings - Fork 554
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
Filtering on listNotifications #3225
Conversation
@@ -417,6 +417,84 @@ describe('notification views', () => { | |||
), | |||
).toBe(true) | |||
expect(forSnapshot(notifs.data)).toMatchSnapshot() | |||
await agent.api.app.bsky.notification.putPreferences( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this was really weird - i was getting intermittent failures (maybe 1/3 of the time) where updating carol's priority setting would also set alice's to true. I tried for awhile to debug this, but couldn't find the source of it. Verified only one call to mock bsync & that's the only place that I could find where this is updated.
I ended up just adding this call to revert carol's priority setting after the test which is just kinda nice tidiness in the test suite anyway but unblocked this flaky test.
If anyone has ideas on what could be happening plz drop them!
Implementation for: #3222
Filter notifications by provided
reason
. Since this will often dramatically reduce the result set, we also add in some logic for paginating on the server side. Right now, we paginate until one of 3 conditions are met:limit
We can adjust the first to numbers if we find the current configuration isn't working as we like