-
Notifications
You must be signed in to change notification settings - Fork 881
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
feat: expand entry read history #377
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I feel like a dropdown menu would be more appropriate here, using a modal would make it feel very cut off. |
But the number of read history user IDs can be up to 100 now. https://github.com/RSSNext/follow-server/commit/7930d7370b4a408ec1f5f56c2e45cecca8872350 Or do we revert it and keep it 20? |
I do not know why. When I use |
I will fix that |
There is no problem with increasing the number of history records on the server side. On the front end, it doesn't make sense to get to 100 records directly. Because in many cases users don't click More to see more users, the conversion rate is very low. So to reduce the size of the data transfer and the pressure on the database itself. We should remove the In other words, there should be no read-histories queries or data in |
Got it, I'll take care of this part |
Signed-off-by: Innei <i@innei.in>
@hyoban I fix this bug |
Signed-off-by: Innei <i@innei.in>
@hyoban I'll merge it first, and then we can start a new branch to implement the above functionality. |
Description
ScreenShot.2024-09-13.15.13.38.2.mp4
Linked Issues
Fixes #370
Fixes https://linear.app/follow-app/issue/FOL-126/follower过多无法展开
Additional context
https://github.com/RSSNext/follow-server/commit/7930d7370b4a408ec1f5f56c2e45cecca8872350