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 #18] [MERGED] [rss] Allow RSS Feeds without "published" Field #25

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

📋 Pull Request Information

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

Base: main ← Head: rss-allow-feeds-without-published-field

📝 Commits (1)

  • df76237 [rss] Allow RSS Feeds without "published" Field

📊 Changes

1 file changed (+7 additions, -2 deletions)

View changed files

📝 supabase/functions/_shared/feed/rss.ts (+7 -2)

📄 Description

If a RSS feed entry did not contain a "published" field, we skipped the entry and didn't added it to the database. Now it is also possible to use feeds without a "published" field. If a feed entry does not contain the field it must contain a "updated" field, which we then use for the "publishedAt" field in the database. If a feed entry doesn't contain one of the two fields the entry is still skipped.

🔄 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/18 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 10/3/2023 **Status:** ✅ Merged **Merged:** 10/3/2023 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `rss-allow-feeds-without-published-field` --- ### 📝 Commits (1) - [`df76237`](https://github.com/feeddeck/feeddeck/commit/df7623748d103f54f9a0a656c24d074d27f2fb40) [rss] Allow RSS Feeds without "published" Field ### 📊 Changes **1 file changed** (+7 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `supabase/functions/_shared/feed/rss.ts` (+7 -2) </details> ### 📄 Description If a RSS feed entry did not contain a "published" field, we skipped the entry and didn't added it to the database. Now it is also possible to use feeds without a "published" field. If a feed entry does not contain the field it must contain a "updated" field, which we then use for the "publishedAt" field in the database. If a feed entry doesn't contain one of the two fields the entry is still skipped. <!-- 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:52 -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#25
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?