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

For validation, and doing server side computation must update all associated changed records

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

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
rails, ruby
領域
backend

研究方向

先追蹤 gather_records 路徑,以及驗證期間和 server_methods 中使用的儲存行為。確定如何透過旗標暫時強制儲存所有已變更的相關記錄,然後驗證一般的父記錄儲存仍保留現有行為。

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

描述

In commit 36516765f840eade6a8862682dd5a12774b259cd a fix was made so that ActiveRecord#changed? would accept optionally the attribute that was changing. I.e. Job.changed? means anything in the job changes, vs Job.changed(:name) means did the name attribute change.

Before Job.changed?(:name) was returning the same as Job.changed?

When this fix was made the gather_records method stopped including has_many records that had changed when gathering the parent during a save. This is actually correct behavior according to Rails. However it is a breaking deprecation for some apps BTW.

The bigger problem is that during validations or computations of server_methods we DO want to save (temporarily) ALL related changed records so the computations can use any values that have changed on the client during the server computation.

So we need a flag (perhaps it is the same as the force flag) that can be used to force ALL related changed records to be saved.

主要語言
JavaScript
星號
538
分支
41
PR 合併指標
30 天內沒有已合併 PR

貢獻指南

開啟貢獻指南

從這裡開始

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

hyperstack-org/hyperstack 的其他 Issue

查看 hyperstack-org/hyperstack 的全部 Issue

相似的 Issue

更多 JavaScript Issue

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

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