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 #73] [MERGED] [core] Fix Decoding of Special Characters #77

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

📋 Pull Request Information

Original PR: https://github.com/feeddeck/feeddeck/pull/73
Author: @ricoberger
Created: 11/24/2023
Status: ✅ Merged
Merged: 11/24/2023
Merged by: @ricoberger

Base: main ← Head: core-fix-decoding-of-special-characters

📝 Commits (1)

  • df4d13d [core] Fix Decoding of Special Characters

📊 Changes

9 files changed (+192 additions, -48 deletions)

View changed files

📝 supabase/functions/add-source-v1/index.ts (+36 -9)
📝 supabase/functions/delete-user-v1/index.ts (+24 -6)
📝 supabase/functions/generate-magic-link-v1/index.ts (+16 -4)
📝 supabase/functions/image-proxy-v1/index.ts (+12 -3)
📝 supabase/functions/profile-v1/index.ts (+40 -10)
📝 supabase/functions/profile-v2/github.ts (+20 -5)
📝 supabase/functions/profile-v2/index.ts (+20 -5)
📝 supabase/functions/stripe-create-billing-portal-link-v1/index.ts (+12 -3)
📝 supabase/functions/stripe-create-checkout-session-v1/index.ts (+12 -3)

📄 Description

We have to add the "charset" parameter to the "Content-Type" header when we return json from one of the Supabase functions, so that special characters are properly decoded in Flutter.

🔄 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/73 **Author:** [@ricoberger](https://github.com/ricoberger) **Created:** 11/24/2023 **Status:** ✅ Merged **Merged:** 11/24/2023 **Merged by:** [@ricoberger](https://github.com/ricoberger) **Base:** `main` ← **Head:** `core-fix-decoding-of-special-characters` --- ### 📝 Commits (1) - [`df4d13d`](https://github.com/feeddeck/feeddeck/commit/df4d13d0b5bc5af5cd24a08a9b2520eab0ecb5f3) [core] Fix Decoding of Special Characters ### 📊 Changes **9 files changed** (+192 additions, -48 deletions) <details> <summary>View changed files</summary> 📝 `supabase/functions/add-source-v1/index.ts` (+36 -9) 📝 `supabase/functions/delete-user-v1/index.ts` (+24 -6) 📝 `supabase/functions/generate-magic-link-v1/index.ts` (+16 -4) 📝 `supabase/functions/image-proxy-v1/index.ts` (+12 -3) 📝 `supabase/functions/profile-v1/index.ts` (+40 -10) 📝 `supabase/functions/profile-v2/github.ts` (+20 -5) 📝 `supabase/functions/profile-v2/index.ts` (+20 -5) 📝 `supabase/functions/stripe-create-billing-portal-link-v1/index.ts` (+12 -3) 📝 `supabase/functions/stripe-create-checkout-session-v1/index.ts` (+12 -3) </details> ### 📄 Description We have to add the "charset" parameter to the "Content-Type" header when we return json from one of the Supabase functions, so that special characters are properly decoded in Flutter. <!-- 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:56:51 -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#77
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?