mirror of
https://github.com/feeddeck/feeddeck.git
synced 2026-03-09 15:12:10 -05:00
[PR #21] [MERGED] [core] Use Published Date for Item Ingestion #28
Reference in New Issue
Block a user
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?
📋 Pull Request Information
Original PR: https://github.com/feeddeck/feeddeck/pull/21
Author: @ricoberger
Created: 10/8/2023
Status: ✅ Merged
Merged: 10/8/2023
Merged by: @ricoberger
Base:
main← Head:core-use-published-date-for-item-ingestion📝 Commits (1)
07d2985[core] Use Published Date for Item Ingestion📊 Changes
10 files changed (+362 additions, -152 deletions)
View changed files
📝
supabase/functions/_shared/feed/googlenews.ts(+36 -16)📝
supabase/functions/_shared/feed/mastodon.ts(+32 -14)📝
supabase/functions/_shared/feed/medium.ts(+36 -16)📝
supabase/functions/_shared/feed/nitter.ts(+36 -16)📝
supabase/functions/_shared/feed/podcast.ts(+33 -9)📝
supabase/functions/_shared/feed/reddit.ts(+36 -16)📝
supabase/functions/_shared/feed/rss.ts(+44 -17)📝
supabase/functions/_shared/feed/stackoverflow.ts(+37 -16)📝
supabase/functions/_shared/feed/tumblr.ts(+36 -16)📝
supabase/functions/_shared/feed/youtube.ts(+36 -16)📄 Description
For the item ingestion logic we are now also looking at the published date for all entries in a RSS feed. If the published date is older then the last update date of a source the item will be skipped. This way we should reduce the number of duplicated items, where an entry was updated in the RSS feed, so that it had a new id and was written again to the database and not only updated.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.