github-starred/feeddeck
2
0
Fork 0
mirror of https://github.com/feeddeck/feeddeck.git synced 2026-03-09 07:02:01 -05:00
Code Issues 5 Packages Projects Releases 8 Wiki Activity

[PR #22] [MERGED] [core] Fix Update of Read State for Large List of Items #29

New Issue
Closed
opened 2025-10-31 16:55:57 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-10-31 16:55:57 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/22
Author: @ricoberger
Created: 10/8/2023
Status: ✅ Merged
Merged: 10/8/2023
Merged by: @ricoberger

Base: main ← Head: core-fix-update-of-read-status-for-large-list-of-items

📝 Commits (1)

  • f7efda4 [core] Fix Update of Read State for Large List of Items

📊 Changes

1 file changed (+15 additions, -6 deletions)

View changed files

📝 app/lib/repositories/items_repository.dart (+15 -6)

📄 Description

When a user scrolls through a list of items and loads more items via the "Load More" button and then clicks on the mark all items as read button, it could happen that the request fails, because Supabase can not handle the update filter with a large list of item ids.

To avoid this error we are splitting the list of item ids provided in the "updateReadStates" into chunks of 25 items for the in clause in the update filter.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/feeddeck/feeddeck/pull/22 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 10/8/2023 **Status:** ✅ Merged **Merged:** 10/8/2023 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `core-fix-update-of-read-status-for-large-list-of-items` --- ### 📝 Commits (1) - [`f7efda4`](https://github.com/feeddeck/feeddeck/commit/f7efda42142621e846d52ee3459299be66a1e9cb) [core] Fix Update of Read State for Large List of Items ### 📊 Changes **1 file changed** (+15 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `app/lib/repositories/items_repository.dart` (+15 -6) </details> ### 📄 Description When a user scrolls through a list of items and loads more items via the "Load More" button and then clicks on the mark all items as read button, it could happen that the request fails, because Supabase can not handle the update filter with a large list of item ids. To avoid this error we are splitting the list of item ids provided in the "updateReadStates" into chunks of 25 items for the in clause in the update filter. <!-- Keep PR title verbose enough and add prefix telling about what source it touches e.g "[rss] Add feature xyz" or if the the PR is not realated to a source use "[core]", e.g. "[core] Fix xyz". If you add a breaking change within your PR you should add ":warning:" to the title, e.g. ":warning: [core] My breaking change" --> <!-- Description of what have been changed. Please also reference an issue, when available. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-10-31 16:55:57 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
enhancement
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/feeddeck#29
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?