Notification endpoints and search debouncing in bloom
By RepoJournal , from @bgrgndzz's public GitHub activity
Backfilled
Buğra Gündüz built out the notification API surface and fixed how search responds to user input across four commits to bgrgndzz/bloom.
He created notification list and count API endpoints [1], then wired them into the application [2]. This gave the app a way to fetch and display user notifications. On the interaction side, he resolved issues with the unlike and unfollow system [3], ensuring those operations worked correctly. He also switched the search input from throttling to debouncing [4], a change that makes the search respond less aggressively to rapid typing.
One email a day. Unsubscribe in one click.
A short briefing every day bgrgndzz ships something — in about 3 minutes.
One email a day. Unsubscribe in one click. Read a past issue →
References
- [1] create notification list and count api endpoints bgrgndzz/bloom
- [2] connect notifications api to the app bgrgndzz/bloom
- [3] resolve issues with the unlike/unfollow system bgrgndzz/bloom
- [4] debounce search instead of throttling bgrgndzz/bloom