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

[PR #128] [MERGED] [core] Make Log Level Configurable #129

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

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/128
Author: @ricoberger
Created: 2/2/2024
Status: ✅ Merged
Merged: 2/2/2024
Merged by: @ricoberger

Base: main ← Head: core-make-log-level-configurable

📝 Commits (1)

  • 57e19c4 [core] Make Log Level Configurable

📊 Changes

6 files changed (+40 additions, -3 deletions)

View changed files

📝 supabase/.env.example (+2 -0)
📝 supabase/functions/_cmd/tools/tools.ts (+1 -0)
📝 supabase/functions/_cmd/worker/worker.ts (+1 -0)
📝 supabase/functions/_shared/feed/utils/getAndParseFeed.ts (+6 -3)
📝 supabase/functions/_shared/utils/constants.ts (+3 -0)
📝 supabase/functions/_shared/utils/log.ts (+27 -0)

📄 Description

The log level is now configurable, via the FEEDDECK_LOG_LEVEL environment variable. The environment variable can have the following values: debug, info, warning or error.

With this change we also only log the response when getting and parsing the feed fails when the log level is set to debug, also when the actual message is still an error. This should reduce the noice in the logs a lot and allows us to specially turn this on while debugging.

🔄 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/128 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 2/2/2024 **Status:** ✅ Merged **Merged:** 2/2/2024 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `core-make-log-level-configurable` --- ### 📝 Commits (1) - [`57e19c4`](https://github.com/feeddeck/feeddeck/commit/57e19c4690a0536fcc4c02543dc0c1f856288df6) [core] Make Log Level Configurable ### 📊 Changes **6 files changed** (+40 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `supabase/.env.example` (+2 -0) 📝 `supabase/functions/_cmd/tools/tools.ts` (+1 -0) 📝 `supabase/functions/_cmd/worker/worker.ts` (+1 -0) 📝 `supabase/functions/_shared/feed/utils/getAndParseFeed.ts` (+6 -3) 📝 `supabase/functions/_shared/utils/constants.ts` (+3 -0) 📝 `supabase/functions/_shared/utils/log.ts` (+27 -0) </details> ### 📄 Description The log level is now configurable, via the `FEEDDECK_LOG_LEVEL` environment variable. The environment variable can have the following values: `debug`, `info`, `warning` or `error`. With this change we also only log the response when getting and parsing the feed fails when the log level is set to `debug`, also when the actual message is still an error. This should reduce the noice in the logs a lot and allows us to specially turn this on while debugging. <!-- 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:57:55 -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#129
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?