Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Update: Working on FeedLand API, making change in how users table works

未關閉
#32 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
15/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
mysql
領域
api, database

研究方向

The issue names database.setUserPrefs but no source file or test. Start by locating that entry point and its callers, including feedlandHome and the markTwain prototype; done would require a maintainer-defined regression check that omitted preferences do not overwrite existing user values.

由索引模型根據 Issue 內容生成。

描述

Hopefully there will be no breakage from this change, which I'm making very carefully.

First a bit of background.

  1. I'm working on a REST API for FeedLand, so we can build other UIs for the data in a feedland instance.
  2. I have a prototype app whose codename is markTwain. You will hear me refer to it from time to time.
  3. markTwain doesn't do everything feedlandHome does (that's the app that forms the UI for FeedLand as you use it now).
  4. So when you assign to the user's prefs, we don't have values for all the things we keep track of for users.
  5. As-written database.setUserPrefs will set the values of all columns, even if they weren't specified by the caller.
  6. This isn't a problem for feedlandHome because it always sends all the values.
  7. But it is a problem for markTwain. So I changed the functionality slightly so that if we don't have a value we don't change it to NULL which is what MySQL would substitute. (I investigate this thoroughly, hopefully.)

markTwain is a placeholder for "all future apps." I could have made MT supply all the values it doesn't do anything with, but this isn't very futuristic. I want to lay a good clean foundation here.

This change should not affect current FeedLand installations, but we should keep an eye out for problems.

I'll post a note in this thread when the changes are deployed.

主要語言
HTML
星號
11
分支
4
PR 合併指標
30 天內沒有已合併 PR

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

scripting/feedlandInstall 的其他 Issue

查看 scripting/feedlandInstall 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。